[Utility][RPC][CLI] Querying governance parameters (Issue #619)

[h5law]

Description

This PR introduces the ability to query v1/query/allChainParmas with a GET request in order to retrieve the current values for all governance parameters stored in the node's PostgreSQL database. This is defined in the OpenAPI YAML RPC specification and its logic is implemented in rpc/handlers.go

The CLI endpoint is a subcommand under the System command that allows for the querying of this RPC endpoint and is used by the make target query_node_params to quickly enable the querying of governance parameters on localnet.

In addition to this the GovParamMetadatMap has been moved to shared/utils/gov_utils.go where it is being initialised and used in persistance and utility. The owner tags have been added to the genesis.proto file to show which parameters own which, this allows for an easy lookup and reduces the code footprint of the getParamOwner function greatly.

There has also been a lot of code cleanup in utility simplifying governance parameter accessor functions and their tests

Issue

Fixes #619

Type of change

Please mark the relevant option(s):

• New feature, functionality or library
• Bug fix
• Code health or cleanup
• Major breaking change
• Documentation
• Other

List of changes

• Add GetAllParams() function to the persistence read interface to retrieve the current value of each parameter
• Add the v1/query/allChainParams RPC endpoint to the RPC specification, and implement its logic
• Add the Query subcommand in the CLI
• Add the AllChainParams subcommand to the Query CLI endpoint to query v1/query/allChainParams
• Add make query_chain_params target to easily query the parameters on a localnet
• Move parameter metadata logic into shared/utils/gov.go
• Reduce code footprint of gov parameters, their accessor functions and tests

Testing

• make develop_test
• LocalNet w/ all of the steps outlined in the README

Required Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added, or updated, godoc format comments on touched members (see: tip.golang.org/doc/comment)
• I have tested my changes using the available tooling
• I have updated the corresponding CHANGELOG

If Applicable Checklist

• I have updated the corresponding README(s); local and/or global
• I have added tests that prove my fix is effective or that my feature works
• I have added, or updated, mermaid.js diagrams in the corresponding README(s)
• I have added, or updated, documentation and mermaid.js diagrams in shared/docs/* if I updated shared/*README(s)

[Olshansk]

👨‍⚖️ 👍

[cr-gpt]

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables for this repo. you could follow readme for more information

The check succeeded, dismissing the review comment.

[reviewpad]

AI-Generated Summary: This pull request introduces several changes across multiple files, primarily focused on refactoring and improving the retrieval and handling of governance parameters. Key changes include the replacement of specific accessor functions with more generic getGovParam calls, the introduction of new utility functions and test cases for governance parameters, and the addition of new API endpoints and RPC functions for querying data. The code has been made more maintainable, modular, and efficient through these updates, and additional functionality has been provided for querying on-chain data and handling metadata from protobuf-generated structures. Updates to the CHANGELOG.md files document the version changes and features introduced in these updates.