chore: use Tempo testnet tag for changesets verification

[struong]

motivation

Tempo tests in the changesets CI workflow were failing because they were using the latest Docker image tag for prool, which currently has breaking changes with what's in testnet. This blocks version cuts.

Following a similar pattern from tempo-apps#363, we can fetch the current testnet Tempo version and use that for testing to ensure compatibility.

change

• Added get-tempo-testnet-tag job to the changesets workflow that fetches the current testnet Tempo image SHA
• Updated the verify workflow to accept an optional tempo-tag input parameter
• Test job in verify consumes testnet tag when available, otherwise defaults to latest

what's next?

If non-changeset tests should also run against current testnet we can apply the same strategy in the verify workflow and/or local tests as well.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 82e4a11

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[jxom]

Superseded by 052d669