[Infra] Allow to programmatically scale actors on DevNet

[okdas]

Objective

In order to thoroughly test the network, we need a way to programmatically provision and remove nodes on the network. This is a requirement for, for example, a state sync end-to-end test.

Origin Document

Identified the requirement for this during #829.

Goals

• A way to easily change infrastructure during end-to-end tests.

Deliverable

• An HTTP endpoint that accepts the name of the actor and the desired number of nodes.
• As a consequence of that feature, we can scale network through the UI. Add that feature to the dashboard.
• Update documentation to reflect the changes to scaling procedure, include information about HTTP endpoint and the UI.

General issue deliverables

• Update the appropriate CHANGELOG(s)
• Update any relevant local/global README(s)
• Update relevant source code tree explanations
• Add or update any relevant or supporting mermaid diagrams

Testing Methodology

• Task specific tests or benchmarks: make ...
• New tests or benchmarks: make ...
• All tests: make test_all
• LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md
• k8s LocalNet: verify a k8s LocalNet is still functioning correctly by following the instructions here

---

Creator: @okdas
Co-Owners: N/A

[okdas]

I realized this has not been captured by the ticket on a dashboard, will add more details soon.

[okdas]

The feature has been implemented, I'm updating the documentation to reflect new changes.

[Olshansk]

The feature has been implemented, I'm updating the documentation to reflect new changes.

Thanks for the update!

[okdas]

• Updated documentation in Notion.
• Updated protocol-infra documentation to include the image: https://github.com/pokt-network/protocol-infra#scaling
• Updated Dashboard repo with examples on how to scale programmatically via HTTP API: https://github.com/pokt-network/v1-explorer-dev#network-api

[Olshansk]

@okdas Can you please also update the main README in this repo to point to all the other docs / READMEs?

For example:

• README.md
• docs/development/README.md
• docs/learning/README.md

I'm 100% no one will complain about the redundancy of backlinks.

[Olshansk]

Also @okdas , did you get anyone else to review the documentation in the other places to make sure it works, is clear and functional?

[okdas]

Good call, I'm on it - I'll update the main repo README files as well. The dashboard has not been integrated with the LocalNet yet, though! That PR will be a good place to get feedback on documentation.