[Testing, Tooling] refactor: in-memory network usage

[bryanchriswhite]

Summary

Human Summary

Refactors usage of in-memory network in tests to utilize updated in-memory network testutils.

Issue

• [Protocol] MVP implementation off the on-chain SubmitProof message handling #141
• [Supplier] refactor: claim & proof protobufs + #263
• [Supplier] refactor: supplier module keys #264
• [Supplier] refactor: supplier module errors #265
• [Testing, Tooling] chore: in-memory network interface & config types #289
• [Testing, Tooling] feat: implement in-memory networks #290
• 👉 THIS PR 👈
• [Supplier] refactor: proof store indices #266
• [Supplier] feat: persistence proofs in submit proof msg handler #250

Type of change

Select one or more:

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

Testing

• Run all unit tests: make go_develop_and_test
• Run E2E tests locally: make test_e2e
• Run E2E tests on DevNet: Add the devnet-test-e2e label to the PR. This is VERY expensive, only do it after all the reviews are complete.

Sanity Checklist

• I have tested my changes using the available tooling
• I have performed a self-review of my own code
• I have commented my code, updated documentation and left TODOs throughout the codebase

[h5law]

One minor comment on naming confusion as we use an SDK and provide an SDK

Otherwise great refactoring!

Love the new pattern, this is truly 🔥:

memnet := sessionnet.NewInMemoryNetworkWithSessions(
		t, &network.InMemoryNetworkConfig{
			NumSuppliers:            2,
			AppSupplierPairingRatio: appSupplierPairingRatio,
		},
	)
memnet.Start(ctx, t)

net := memnet.GetNetwork(t)

[bryanchriswhite]

Unintentionally closed, will re-open as a new PR.

UPDATE:

• [Testing, Tooling] refactor: in-memory network usage #307