feat: Move CommunityPool to its own module

[likhita-809]

Description

Closes: #10811

This PR does the following:

• Makes a separate pool module on its own to handle community pool services
• Completely removes the dependency of x/distribution module in x/gov
• Removes CLI cmds related to pool in x/distribution client cmds i.e., fund-community-pool cmd
• Adds new msg service and grpc query routers in x/distribution to handle community pool msg and query services

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• run make lint and make test
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[julienrbrt]

I know the PR isn't ready, but just a small note already, we need to follow this check-list when adding a new go.mod: https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#gomod

[julienrbrt]

lgtm! 🚀
Just missing the nit for proposal simulations.

[fedekunze]

the fund community pool message should be removed in favour of just using a send transaction. Have you consider this as part of this implementation?

[julienrbrt]

the fund community pool message should be removed in favour of just using a send transaction. Have you consider this as part of this implementation?

That's the case now, x/protocolpool is just a module account. We theoretically do not need the MsgFundCommunityPool message.