Adding a custom lint rule to ensure we use v-clean-tooltip instead of v-tooltip directives.

[codyrancher]

Summary

Wanted to automate the ability to detect one of our common sources of XSS issues. I wrote a custom linter rule so we can catch this in CI.

Technical notes summary

I noticed that we currently exclude linting rancher-components from our root directory. I'd think we'd just want to include everything but I'm not sure.

Areas or cases that should be tested

None, it's in a way an additional test.

Areas which could experience regressions

None

Screenshot/Video

Example:

You can disable the rule in the template using:

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