[red-knot] Property test workflow: Fix issue label, link to CI run

[sharkdp]

Summary

See title. Had to make a minor change, because it failed the zizmor pre-commit check otherwise (FYI @AlexWaygood)

error[template-injection]: code injection via template expansion
  --> /home/shark/ruff/.github/workflows/daily_fuzz.yaml:68:9
   |
68 |          - uses: actions/github-script@v7
   |  __________^
69 | |          with:
70 | |            github-token: ${{ secrets.GITHUB_TOKEN }}
71 | |            script: |
   | | ___________^
72 | ||             await github.rest.issues.create({
...  ||
77 | ||               labels: ["bug", "parser", "fuzzer"],
78 | ||             })
   | ||               ^
   | ||_______________|
   |  |_______________this step
   |                  github.server_url may expand into attacker-controllable code
   |
   = note: audit confidence → High

[AlexWaygood]

See title. Had to make a minor change, because it failed the zizmor pre-commit check otherwise (FYI @AlexWaygood)

Ooh interesting. @woodruffw could that context field really be controlled by an attacker...? That feels like it might be a false positive to me? :-)

(Docs here)

[AlexWaygood]

Thanks!! Hardcoding github.com seems very unlikely to break, whether or not the zizmor diagnostic is a false positive 😄

[woodruffw]

Ooh interesting. @woodruffw could that context field really be controlled by an attacker...? That feels like it might be a false positive to me? :-)

Yep, that looks like a false positive! Thanks for the ping!