Use outputs of `command` as step outputs

[ffisc]

Describe the bug

It would be great it this worked

- id: step_1
    uses: nick-fields/retry@v3
    with:
      command: echo "foo=bar" >> $GITHUB_OUTPUT
- run: echo ${{ steps.step_1.outputs.foo }}

Expected behavior
See above

Screenshots
N/A

Logs
N/A

[AvivPeledTalon]

My team would also benefit from that.
I'm guessing it has to do with the fact that the action has some declared outputs and our new outputs aren't on the list (probably not nick-fields' fault but has more to do with Github actions' design)

[AvivPeledTalon]

What I ended up doing is using GITHUB_ENV instead of GITHUB_OUTPUTS to get data out of the retry action