Allow HMR in Rancher Components and Harvester

[rak-phillip]

Summary

This allows HMR to trigger when changes are made to Rancher Components and Harvester by omitting the excludes argument from getWatcherIgnored(). Watch and WatchOptions work to allow Webpack to watch files and recompile whenever they change - I don't see any benefit in excluding Rancher Components and Harvester from this process by default.

As I understand, the excludes variable exists to control production builds; this change will only affect development.

This also includes a change to clean up the appConfig param in shell/vue.config.

The prefix _ is a convention to indicate that a parameter is expected, but unused within a function. We make use of appConfig in the default export, so we can remove the _ and supply a default value for appConfig if nothing is passed.

Areas or cases that should be tested

• HMR triggers when running development builds and modifying Rancher Components/Harvester

Areas which could experience regressions

Perhaps, we were intentionally excluding these from HMR for a reason that I'm not aware of.

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

[rak-phillip]

@torchiaf I'm requesting a review from you because harvester is included the the default excludes as well¹. I'm unsure if there are some historical reasons why we would want to omit Harvester directories from HMR.

Footnotes

1. https://github.com/rancher/dashboard/blob/05462046a3c3680745ff997c378d7be8686e6ffa/vue.config.js#L5 ↩