Feat: JSdoc Eslint Plugin

[callinmullaney]

Summary Adds a new plugin to existing Eslint setup that allows us to check formatting of javascript comments. See: https://jsdoc.app/about-getting-started.html

Explain the motivation for making this change. What existing problem does the pull request solve?

• JS commenting can vary greatly between components or not be present at all. This plugin allows us to enforce a standard that is easy to read and useful for new devs to understand existing component JS.

Documentation Update (required)

• No documentation updates are needed. This new plugin automatically runs when npm run lint-js is fired.

How to review this PR

• [x] Checkout branch and run npm install
• [x] run npm run lint-js and verify you see the following warnings related to the existing Tabs component.
• [x] Verify the file changes look appropriate and we are extended the recommended rules found here: https://github.com/gajus/eslint-plugin-jsdoc#configuration
• [x] Once the above is test please comment in the PR and I will then include a commit that fixes those warnings for our Tab component.

[ryanhagerty]

@callinmullaney LGTM - feels like Typescript Lite.

Since this is open-source, I'm def for this kind of documentation. But as an unrelated aside, I'm hesitant about this in client projects - at least at the level of recommended settings. I'm not sure a six line function whose greatest complexity is click needs a seven line comment. 😵‍💫

Anywho, that's just my grumbly old man comment, good job getting this set up 🍟

[callinmullaney]

ToDo: Add documentation to the README regarding this linting addition. Link to JSdoc plugin, how to use it, and how to disable it completely.

[github-actions[bot]]

:tada: This PR is included in version 1.7.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: