Fixes an issue where create Astro doesn't respect custom npm registries

[calebdwilliams]

Changes

• Introduced a fix for create-astro: set custom registry during project scaffold #7279 by introducing a utility to check the preferred package manager config to find any custom package registry, defaulting to the public npm registry (which is currently in use)

Testing

I'm not sure how to effectively test this fix without affecting the entire build process. Happy to accept suggestions.

Docs

This should enable Astro to behave as expected for users with custom package registries (such as large enterprises who might block the public npm registry for security or efficiency reasons).

[changeset-bot]

🦋 Changeset detected

Latest commit: 0ff4be4

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[natemoo-re]

This looks great, thanks for the PR!

Discussed on Discord and confirmed locally that these changes work both when a user has set a custom registry and when a user has no custom registry defined. Package managers properly return the default NPM registry in the latter case.