WHY are these changes introduced?

Fixes #1868

node-fetch follows redirects always with GET. The HTTP Spec allows this for historical reasons.

This behavior is problematic, when trying to access a shop's API when only a custom domain is given.

• Custom domain: example.com
• My Shopify domain: custom-1234.myshopify.com
  The request to the GraphQL API fails, because the request is redirected from the custom domain to the My-Shopify domain. During this redirect, node-fetch swaps the method to GET which results in a 404 response.

WHAT is this pull request doing?

This pull request implements a node-fetch fetch wrapper that handles redirects manually.

Type of change

• Patch: Bug (non-breaking change which fixes an issue)
• Minor: New feature (non-breaking change which adds functionality)
• Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• I have used pnpm changeset to create a draft changelog entry (do NOT update the CHANGELOG.md files manually)
• I have added/updated tests for this change
• I have documented new APIs/updated the documentation for modified APIs (for public APIs) (comment: needed?)