[Application] Single Service Applications

[red-0ne]

Summary

This PR enforces staking Applications to have a single service, updates the tests and add documentation about the reasoning behind this enforcement.

Note that the Application.ServiceConfigs remains a slice, reducing the codebase diff and allowing future multi-service Applications

Issue

Having MaxClaimableAmount = Application.Stake * numSessionSuppliers could allow Applications to over-service by making Suppliers of different session claim from the same stake.

• [Docs] Tokenomics Documentation #750 (comment)

Type of change

Select one or more from the following:

• New feature, functionality or library
• Documentation

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

[bryanchriswhite]

[github-actions]

The CI will now also run the e2e tests on devnet, which increases the time it takes to complete all CI checks.

You may need to run make trigger_ci to submit an empty commit that'll trigger the tests.

GCP workloads (requires changing the namespace to 886)
Grafana network dashboard for devnet-issue-886

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
12819930	Triggered	Generic Password	57e7f8c	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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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.}

[bryanchriswhite]

Preemptively approving! +1 to outstanding feedback, plus one question; otherwise, LGTM! 🙌

[Olshansk]

Ty!