[Docs] Untrack and auto-generate params.md on docusaurus_start

[bryanchriswhite]

Summary

• Remove docusaurus/docs/protocol/governance/params.md from version control because it is [generated automatically on deployment], which allows the published version to get out of sync with what's in git.
• Add docusaurus/docs/protocol/governance/params.md to .gitignore so that it ignored going forward.
• Add docs_update_gov_params_page as a dependency to the docusaurus_start so that params.md is available when building and serving docusaurus locally.

Issue

#933 (review)

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

[Olshansk]

What if we keep it in version control but also build it in docusarus_start?

I'd like to maintain both to avoid "ephemeral docs"

[bryanchriswhite]

What if we keep it in version control but also build it in docusarus_start?

I'd like to maintain both to avoid "ephemeral docs"

If we do that, there would still be a possibility that version control gets out of sync with what's deployed unless we also add a CI check which make docs_update_gov_params_page (or docusaurus_start) and fails if any markdown files change in the docusaurus directory.

[Olshansk]

@bryanchriswhite

• Things I feel strongly about: not having this README as part of version control. This impacts searchability, indexing, etc...
• Things I feel less strongly about: things being out of sync.
• Things I do not think are a high priority but can be done in the future: automation to ensure things don't get ouf of sync.

Wdyt of just adding a TODO to add the check you mentioned (it's ULTRA LOW priority) and closing this PR w/o merging?