New: allows plugins to specify the URLs to their docs (fixes #6582)

[pmcelhaney]

This is a first pass at implementation. I'm putting it out now to get feedback. Will come back and write a proper commit message.

[eslintbot]

Thanks for the pull request, @pmcelhaney! I took a look to make sure it's ready for merging and found some changes are needed:

• The commit summary needs to begin with a tag (such as Fix: or Update:). Please check out our guide for how to properly format your commit summary and update it on this pull request.
• Pull requests with code require an issue to be mentioned at the end of the commit summary, such as (fixes #1234). Please update the commit summary with an issue (file a new issue if one doesn't already exist).

Can you please update the pull request to address these?

(More information can be found in our pull request guide.)

[jquerybot]

Thank you for your pull request. It looks like this may be your first contribution to a jQuery Foundation project, if so we need you to sign our Contributor License Agreement (CLA).

📝 Please visit http://contribute.jquery.org/CLA/ to sign.

After you signed, the PR is checked again automatically after a minute. If there's still an issue, please reply here to let us know.

---

If you've already signed our CLA, it's possible your git author information doesn't match your CLA signature (both your name and email have to match), for more information, check the status of your CLA check.

[pmcelhaney]

Lots of useless whitespace. I'll clean this up.

[pmcelhaney]

Thinking it may be useful to pass the problem object as a second argument so the plugin can link to more specific detail about how the rule was violated. An IDE could even fetch the URL and provide contextual help.

But that's another PR for another day.

[eslintbot]

LGTM

[eslintbot]

LGTM

[vitorbal]

thanks for the PR, @pmcelhaney! Adding the "do not merge" label for now while we discuss the details in #6582

[pmcelhaney]

Closing based on feedback from the team.