[WIP][Metrics] Implement onchain cumulative relay_count and compute_units per service_id

[red-0ne]

Summary

Implement service usage metrics tracking for applications and suppliers

Primary Changes:

• Add service_usage_metrics field to both Application and Supplier proto messages
• Create efficient storage mechanism for metrics with separate index stores
• Implement hydration/dehydration pattern to optimize performance when metrics aren't needed
• Update claim processing to track relay volume and compute units per service

Secondary changes:

• Add helper methods to update metrics during claim settlement
• Update application and supplier test fixtures
• Create merge functions for metrics during application transfers

Issue

• Issue_or_PR: [Metrics] Onchain cumulative relay_count and compute_units per service_id #1141

Type of change

Select one or more from the following:

• New feature, functionality or library
• Bug fix
• Code health or cleanup
• Documentation
• Other (specify)

Sanity Checklist

• I have updated the GitHub Issue Metadata: assignees, reviewers, labels, project, iteration and milestone
• For docs: make docusaurus_start
• For small changes: make go_develop_and_test and make test_e2e
• For major changes: devnet-test-e2e label to run E2E tests in CI
• For migration changes: make test_e2e_oneshot
• 'TODO's, configurations and other docs

[Olshansk]

@red-0ne Publishing a very preliminary review.

Relying on @bryanchriswhite to review this as well.

[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 1365)
Grafana network dashboard for devnet-issue-1365

[Olshansk]

@red-0ne This PR:

1. Has gotten huge
2. Is definitely "good enough" for us to iterate
3. Too big for me to give any good feedback at this point
4. I'm getting "PR fatigue" and just want to get it over the finish line.

My only remaining question/concern is about the protocol upgrade.

I'm approving the PR, but is there anything we need to do in vNext?

I realize we're only adding things, so my gut says "no", but I want to be ultra careful about this.

[red-0ne]

@Olshansk

My only remaining question/concern is about the protocol upgrade.

I'm approving the PR, but is there anything we need to do in vNext?

I realize we're only adding things, so my gut says "no", but I want to be ultra careful about this.

I tested it against a localnet migration, worked well by starting to show onchain metrics

[Olshansk]

@red-0ne Per this plan, let's prioritize this in v0.1.28.

[Olshansk]

@red-0ne Moved this to WIP, but we will prioritize getting this in sooner rather than later.

[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 1365)
Grafana network dashboard for devnet-issue-1365