feat: obscure cross-space headers from response errors

[scuilla]

With the use of the extra header for cross-space resolution, errors include an unobscured encoded token map. This applies the same obscuring technique used for the Authorization header to the X-Contentful-Resource-Resolution one.

Example:

{
    "status": 404,
    "statusText": "Not Found",
    "message": "The resource could not be found.",
    "details": {
      "type": "Space",
      "id": "J2Lo0Dwdxt"
    },
    "request": {
      "url": "https://preview.contentful.com:443/spaces/J2Lo0Dwdxt/environments/master/entries",
      "headers": {
        "Accept": "application/json, text/plain, */*",
        "Content-Type": "application/vnd.contentful.delivery.v1+json",
        "X-Contentful-Resource-Resolution": "...9fQ==",
        "X-Contentful-User-Agent": "sdk contentful.js/11.5.4; platform node.js/v22.13.1; os macOS/v22.13.1;",
        "Authorization": "Bearer ...i_KuA",
        "User-Agent": "axios/1.8.1",
        "Accept-Encoding": "gzip, compress, deflate, br"
      },
      "method": "get"
    },
    "requestId": "10621051-215d-55cc-87fa-b00d4f550218"
  }

[contentful-automation]

🎉 This PR is included in version 9.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀