fix: improve npm installation by using pacote for package resolution

[achaljhawar]

• Add pacote dependency for more stable package name resolution
• Update generator.js to use pacote.manifest() instead of internal arborist symbols
• Clean up arborist mock and add new pacote mock for testing

These changes improve package name resolution by using a more stable public API from pacote instead of relying on internal arborist symbols. The changes are focused solely on the package resolution logic, without modifying workflows, arborist version, or supported engines.

Related issue(s)
Resolves #1102

[changeset-bot]

⚠️ No Changeset found

Latest commit: 467b000

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[derberg]

@achaljhawar please resolve the conflicts with master branch

[achaljhawar]

done @derberg

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ItshMoh]

Hey @achaljhawar this test is also failing, look into it.