fix issue with nightly runs tests for extensions

[aalves08]

Summary

Fixes #

Occurred changes and/or fixed issues

• fix issue with nightly runs tests for extensions https://github.com/rancher/dashboard/actions/runs/20286871674/job/58262473319

with the failure of the approach in #16183, let's go for a different idea

Technical notes summary

With the introduction of npm@latest with https://github.com/rancher/dashboard/pull/16166/files, NPM 11.3 introduces stricter checks to the --dry--run for which it includes the version check (should not publish the same published version).

npm/cli#8286

This means that in recent versions of npm (including 11.3.0+), running npm publish --dry-run will still produce warnings or errors if your package configuration has issues, such as:
The package name and version combination already exists in the registry.
Invalid fields in your package.json file that need correction (e.g., invalid scripts).
Missing required metadata for trusted publishing (in version 11.5.1+).

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility
• The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base

[eva-vashkevich]

lgtm but i am not an expert

[aalves08]

@eva-vashkevich thanks! 🙏