[Docs] Update "Adding On-Chain Module Parameters"

[bryanchriswhite]

Summary

Updates "Adding On-Chain Module Parameters" doc to:

1. Reflect recent changes in param update testing (see: [Testing] refractor: param update E2E tests as integration tests #826)
2. Group related steps
3. Improve consistency between and readability of code snippets
4. Fill in gaps:

• Omitted steps/files.
• Adding individual param updates (MsgUpdateParam) to a module which doesn't already support it.

Issue

• [Utility] Minimum staking values for each actor #612
• [Testing] refractor: param update E2E tests as integration tests #826

Type of change

Select one or more from the following:

• New feature, functionality or library
• Consensus breaking; add the consensus-breaking label if so. See [Infra] Automatically add the consensus-breaking label #791 for details
• Bug fix
• Code health or cleanup
• Documentation
• Other (specify)

Testing

• Documentation: make docusaurus_start; only needed if you make doc changes
• Unit Tests: make go_develop_and_test
• LocalNet E2E Tests: make test_e2e
• DevNet E2E Tests: Add the devnet-test-e2e label to the PR.

Sanity Checklist

• I have tested my changes using the available tooling
• I have commented my code
• I have performed a self-review of my own code; both comments & source code
• I create and reference any new tickets, if applicable
• I have left TODOs throughout the codebase, if applicable

[red-0ne]

Finally got this reviewed 🎉 .

I left some NITs but looks good overall.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
12819930	Triggered	Generic Password	8b6b2c5	localnet/kubernetes/observability-prometheus-stack.yaml	View secret
12819930	Triggered	Generic Password	8b6b2c5	localnet/kubernetes/values-pocketdex-postgres.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[red-0ne]

🚢 🇮🇹

[Olshansk]

@bryanchriswhite I left some superficial comments & NITs but will edit when I end up going through the instructions and adding a param myself.

For now, just wanted you to be aware of

+ this is added
- this is removed

[bryanchriswhite]

For now, just wanted you to be aware of

+ this is added
- this is removed

Thank's for the callout! 🙌 I was already aware; however, docusaurus doesn't seem to support it out of the box and adding support required more context than I had and was willing to invest time to acquire at the moment:

Source	Rendered

I looked into it but concluded that I would need to go deeper and get more context on docusaurus than I had/have.

Links:

• Feature request from 2020
  
• Example from a closed issue
• Example from an open issue