chore: Update sepolia example env cert verifier

[ethenotethan]

Fixes Issue

Fixes #

Changes proposed

Updates example env cert verifier address for v2 sepolia to use latest verifier vs legacy.

Screenshots (Optional)

Note to reviewers

[Copilot]

Pull Request Overview

This PR updates the example environment file for Sepolia by replacing the certificate verifier address with a new value.

• Updated the EIGENDA_PROXY_EIGENDA_V2_CERT_VERIFIER_ROUTER_OR_IMMUTABLE_VERIFIER_ADDR value

Comments suppressed due to low confidence (1)

.env.exampleV2.sepolia:50

• [nitpick] The new address uses mixed-case EIP-55 checksumming while the previous one was lowercase. For consistency across your example env files, choose one casing style (e.g., all lowercase or EIP-55 checksummed) and apply it uniformly.

EIGENDA_PROXY_EIGENDA_V2_CERT_VERIFIER_ROUTER_OR_IMMUTABLE_VERIFIER_ADDR=0x58D2B844a894f00b7E6F9F492b9F43aD54Cd4429

[samlaf]

How did we not catch this in tests/CI before your manual tests? Feel like we should add a test to catch these kinds of regressions in the future.

Oh is it because the tests are populated with addresses manually which are different from the ones here? This is another issue with keeping all these different configs everywhere, and why @litt3 was against having these example files.

Is there an easy way we can compare the values here to those hardcoded in the proxy binary and fail if they differ?

[litt3]

How did we not catch this in tests/CI before your manual tests? Feel like we should add a test to catch these kinds of regressions in the future.

Oh is it because the tests are populated with addresses manually which are different from the ones here? This is another issue with keeping all these different configs everywhere, and why @litt3 was against having these example files.

Is there an easy way we can compare the values here to those hardcoded in the proxy binary and fail if they differ?

@samlaf @ethenotethan Maybe instead of having these example files, it would suffice to just have a list of env vars that should be set? That would force users to thoughtfully consider every value, but at least they would know every value that needs to be set for an functioning system. This strategy would also prevent stuff like this address getting out of sync, which is so easy to do when we don't have checks to verify.

[ethenotethan]

@litt3 @samlaf filed a linear issue for tracking