fix: add $DISK_NAME to launch-without-cached-state

[gustavovalverde]

Motivation

Add missing string replacements missing from #7690, and add the $DISK_NAME variable when launching the container

Solution

• Replace all /sbd with /$DISK_NAME
• Add $DISK_NAME before docker run in launch-without-cached-state job

Review

Nothing specific

Reviewer Checklist

• Will the PR name make sense to users?
  • Does it need extra CHANGELOG info? (new features, breaking changes, large changes)
• Are the PR labels correct?
• Does the code do what the ticket and PR says?
  • Does it change concurrent code, unsafe code, or consensus rules?
• How do you know it works? Does it have tests?

[gustavovalverde]

Running a full-sync here to confirm it starts running: https://github.com/ZcashFoundation/zebra/actions/runs/6461129131

We don't have to wait for this to finish, it's preferred to run the full sync from the main branch

[teor2345]

I've bumped this priority down to high so it doesn't interrupt other merging PRs.

[teor2345]

@Mergifyio refresh

[mergify]

refresh

✅ Pull request refreshed

[teor2345]

This PR isn't being queued because this rule isn't satisfied:
all of: [📌 queue conditions of queue batched]
any of: [🛡 GitHub branch protection]
check-success=Zebra tip / Run full-sync-to-tip test

But I can see the patch job in the task list:
CI Docker / Zebra tip / Run full-sync-to-tip test (pull_request) Successful in 2s
Required
Details

@gustavovalverde this might be a weird mergify or workflow bug?

[gustavovalverde]

@teor2345 I triggered a manual full-sync-to-tip from this branch, and it's still running. That might be the reason (?).

[teor2345]

@teor2345 I triggered a manual full-sync-to-tip from this branch, and it's still running. That might be the reason (?).

That seems unlikely, manual syncs have never blocked merging before.

It could be a once-off Mergify bug.