Fix Kurtosis, web3signer and cargo-audit for CI

[michaelsproul]

Issue Addressed

Fix the failing Kurtosis jobs on CI, e.g.

https://github.com/sigp/lighthouse/actions/runs/12226785831/job/34102825704?pr=6669

Proposed Changes

• Kurtosis fix: Remove the -0 that was being erroneously added to the artifact name reference in the doppelganger script. Something must have changed upstream to break this.
• Web3signer fix: update to Java 21.
• Cargo audit: temporarily ignore vuln for idna until upstream patch is available.
• May-as-well: install the latest version of kurtosis-cli, rather than pinning 1.3.1.

[macladson]

Thank you 🙏

[jimmygchen]

There's a breaking change in the new version of Web3Signer - it now requires Java 21 runtime. Created a PR to test the fix:
#6674

[michaelsproul]

Just the flaky network tests failing now. I'll try a merge

[michaelsproul]

@mergify queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

The merge conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ☑️ test-suite-success

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

[michaelsproul]

@mergify requeue

[mergify]

requeue

✅ This pull request will be re-embarked automatically

The followup queue command will be automatically executed to re-embark the pull request

[mergify]

queue

🛑 The pull request has been removed from the queue default

The merge conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ☑️ test-suite-success

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

[jimmygchen]

@mergify requeue

[mergify]

requeue

✅ This pull request will be re-embarked automatically

The followup queue command will be automatically executed to re-embark the pull request

[mergify]

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at e9ec67e