Describe the bug

We were already URL encoding the package names when querying with gh api, and the change in #10384 broke that.

Affected version

2.68.0

Steps to reproduce the behavior

We had a step that looked like this in our action:

run: |
  IMAGE_NAME=$(echo "\"${{ inputs.image-name }}\"" | jq -r @uri)
  SHA=$(gh api \
    -H "Accept: application/vnd.github.v3+json" \
    /orgs/(org-name)/packages/container/$IMAGE_NAME/versions \
    | jq ...)

The action started failing this week as (we assume) more of the GH runners started picking up the new version of gh

Expected vs actual behavior

We expected gh api to (continue to) return package metadata using the request above. Instead we got a 404 message.

Logs

Requests using the latest version of gh returned this error:

gh: Package not found. (HTTP 404)