Bounty module CLI commands

[zeeshanakram3]

This draft PR contains my initial work related to Bounty module CLI commands.

Related issue:

• CLI: Bounty management commands #3056
• CLI: Bounty management commands (bounties related) #3058
• CLI: Bounty management commands (funding related) #3059
• CLI: Bounty management commands (work related) #3060

The purpose of this PR is to add the following Bounty management commands and describe their usage in cli package README.md;

• Get a bounty by id bounty:bounty
• List all bounties bounty:bounties
• Creating a bounty bounty:createBounty
• Canceling a bounty bounty:cancelBounty
• Vetoing a bounty bounty:vetoBounty
• Funding a bounty bounty:fundBounty
• Withdrawing funds from the bounty bounty:withdrawFunding
• Withdraw work entrant funds bounty:withdrawWorkEntrantFunds
• Announcing the work entry for a successful bounty bounty:announceWorkEntry
• Withdraw work entry from a bounty bounty:withdrawWorkEntry
• Get a work entry by id bounty:entry
• List of work entries bounty:entries
• Submitting work for a given bounty bounty:submitWork
• Submitting oracle judgment bounty:submitOracleJudgment

The code that needs double-check/review or has not been implemented is marked with TODO comments.

The implementation details of the initial work are as follows:

• Added JSBounty & BountyMilestone types in the types/src/bounty.ts, these two types were missing in olympia base branch. I named bounty as JSBonuty because augment/augment-api-query.ts already had Bounty imported from Polkadot js treasury.
• The abstract class BountyCommandBase extends RolesCommandBase, defines the helpers function used in the bounties related commands
• bounty:createBounty command ensures that all bounty creation parameters are valid.
• bounty:cancelBounty & bounty:vetoBountycommand ensures that bounty can only be canceled/vetoed if it's in the Created Stage and has zero contributions. Also, bounty can only be canceled by member who created it.
• The bounty stage calculation helper functions are defined to make sure that validations on bounty stage are performed in the following commands: announceWorkEntry, withdrawWorkEntry, submitWork, submitOracleJudgment etc
• Generated correct TS type for submitOracleJudgment extrinsic, previously on TS side oracleJudgment was defined as

enum oracleJudgment { Winner: { reward: number }, Rejected }


However the correct type that runtime extrinsic accepts is 





BTreeMap<EntryId, OracleWorkEntryJudgment> 





where OracleWorkEntryJudgment corresponds to 






enum OracleWorkEntryJudgment  { Winner: { reward: number }, Rejected }

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/joystream/pioneer-testnet/63VKGSBizLCT4N3K6x59HFyjM4jZ
✅ Preview: Canceled

[Deployment for 0a0fd8c canceled]