`deployment-url` output by wrangler/actions is masked, unable to use in the next steps inside actions

I am trying to use the `deployment-url` provided by the `wrangler/action` in a multi-stage Github action workflow.

By using the steps mentioned in the Github actions docs: [Defining and using job outputs](https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/pass-job-outputs#defining-and-using-job-outputs)

**For example:**

```yaml
jobs:
job1:
runs-on: ubuntu-latest
outputs:
output1: ${{ steps.step1.outputs.test }}
output2: ${{ steps.step2.outputs.test }}
steps:
- id: step1
run: echo "test=hello" >> "$GITHUB_OUTPUT"
- id: step2
run: echo "test=world" >> "$GITHUB_OUTPUT"

# Assume job1 is defined as above
job2:
runs-on: ubuntu-latest
needs: job1
steps:
- env:
OUTPUT1: ${{needs.job1.outputs.output1}}
OUTPUT2: ${{needs.job1.outputs.output2}}
run: echo "$OUTPUT1 $OUTPUT2"
```

When consuming/using the output value inside `job2`, the value logs as an empty string.

Start with the documented multi-stage GitHub Actions workflow and the wrangler/action deployment-url output, then trace how the value is passed from job1 to job2. Done means the deployment URL is available as a usable output in the next job rather than appearing as an empty string.

Written by the indexing model from the issue text.