feat: Add support for submitting DAO proposals

[frol]

Currently, commands like near tokens xxx.near send-near prepare a transaction with native actions such as TRANSFER or FUNCTION_CALL to FT contract. I tried to integrate DAO commands right into the existing commands, but with DAO we have two different accounts (DAO contract account id, and signer account id) in addition to a receiver account id (if applicable).

Here is the current command to send NEAR:

near tokens sender.near send-near receiver.near 10N network-config mainnet

If I just try to "send tokens from DAO", there is no way to specify who will be signing the transaction:

near tokens dao.near send-near receiver.near 10N network-config mainnet

So my natural first attempt was:

near dao devdao.near tokens send-near receiver.near 10N sign-as signer.near network-config mainnet

Though, it might mislead users that this command will actually send the tokens while it is only intended to submit a new proposal to the DAO with a TRANSFER action, which will only be executed when the proposal is confirmed. So second thought is to introduce submit-proposal and confirm-proposal commands:

near dao devdao.near submit-proposal send-near receiver.near 10n sign-as signer.near network-config mainnet

The problem I hate to admit is that we won't be able to reuse existing commands, so send-near, send-ft, send-nft, function-call as-transaction, deploy, account manage-storage-deposit deposit / withdraw commands will need to be re-implemented, and it is even more painful if we take extensions into account, e.g. bos CLI components deployment, permissions and prepaid storage management would need to be re-implemented for DAO as well.

At least DAO proposal confirmation seems to be quite straightforward:

near dao devdao.near confirm-proposal 123 gas-attached 200TGAS sign-as signer.near network-config mainnet

I would love to spend more time thinking about how to avoid code duplication, so this issue is just a placeholder for now.

[frol]

Another round of ideas, introduce dao "signing" at the end, so instead of sign-with-... we will have submit-as-dao-proposal sign-as <dao-member-account-id> ...:

near \
  tokens devhub.sputnik-dao.near \
  send-near receiver.near 10N \
  network-config mainnet \
  submit-dao-proposal dao-member.near \
  sign-with-keychain \
  send

Thus, we would need to extend the current src/transaction_signature_options with submit-dao-proposal <signer-account-id> which will in its turn should translate the prepared unsigned transaction into DAO proposal function call (if possible, otherwise fail) and reuse "sign-with-*" -> "send" implementations after.