[P2P] Refactor P2P submodules

[bryanchriswhite]

@Reviewer

This PR may be more digestible / reviewable on a commit-by-commit basis. Commits are organized logically and any given line is only modified in a single commit, with few exceptions*.

(In the interest of preserving the git-time-continuum :police_officer::rotating_light:, this applies in batches of commits between comments or reviews by humans*, only once "in review")

---

Description

Refactor P2P module dependencies as submodules, ultimately to support usage P2P module usage in the CLI.

Issue

Related:

• 730

Dependant(s):

• 891

• 801

• 892

Type of change

Please mark the relevant option(s):

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

List of changes

• decoupled P2P module dependencies from Consensus module (disambiguates modules registry names)
  • added "current_height_provider" module registry slot
  • promoted CurrentHeightProvider to a submodule interface type
  • added consensusCurrentHeightProvider implementation
• promoted Router interface to a submodule interface type
  • added "staked_actor_router" modules registry slot
  • added "unstaked_actor_router" modules registry slot
  • converted backgroundRouter implementation to submodule
  • converted rainTreeRouter implementation to submodule
  • simplified router base config

Testing

• [x] make develop_test; if any code changes were made
• [x] make test_e2e on k8s LocalNet; if any code changes were made
• [x] e2e-devnet-test passes tests on DevNet; if any code was changed
• [ ] Docker Compose LocalNet; if any major functionality was changed or introduced
• [x] k8s LocalNet; if any infrastructure or configuration changes were made

Required Checklist

• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have added, or updated, godoc format comments on touched members (see: tip.golang.org/doc/comment)
• [x] 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)