[Proof] Implement scalable proof validation

[red-0ne]

Summary

This PR refactors proof validation by distributing it across the proof submission workflow for better scalability.

The validation process is divided into two stages:

1. Proof Submission: Ensures the proof is well-formed and adheres to the current on-chain state.
2. Proof Module Endblocker: Handles computationally intensive tasks using self-contained parallel verification. It includes:
   • Relay request and response signature verification.
   • Validation of the ClosestMerkleProof.

Additionally, the proof module endblocker:

• Deletes all the processed proofs
• Reflects the verification result in the corresponding claim's ProofStatus field.

The potential supplier slashing is retained within the SettlePendingClaims flow, ensuring a clear separation of concerns.

Issue

• [Code Health] Improve Claim settlement processing scalability #1013

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

• 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

[github-actions]

The image is going to be pushed after the next commit.

You can use make trigger_ci to push an empty commit.

If you also want to run E2E tests, please add devnet-test-e2e label.

[Olshansk]

@red-0ne I did a first pass of this, but I plan to do a COMPLETE second pass as well.

This is very critical and going to need some work.

[Olshansk]

@red-0ne Ty for taking all of my feedback in the iteration. Looking much better!

I think it should. be g2g after another round of review.

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

[Olshansk]

One more renaming request. Other than that g2g.

Approving prematively!

[Olshansk]

@red-0ne Let's also submit a docs PR w/ the diagram we put together in the other discussion.