Incorrect access control in TreasuryBTC::withdrawForStaking

The function TreasuryBTC::withdrawForStaking has a conflicting access control design: it checks msg.sender == founder || msg.sender == owner(), but the onlyOwner modifier already restricts access to the owner. So, the founder can never call the function if they are not the owner.

function withdrawForStaking(uint256 amount) external onlyOwner {
    require(msg.sender == founder || msg.sender == owner(), "Only founder");
    // ...
}

Remove the onlyOwner modifier.

Nexalo: withdrawForStaking functionality has been completely removed.

Zealynx: If the founder was supposed to have withdrawal access independent of the owner, that's now lost.