[RFC]: Flag when TAB indentation has been used in JSDoc comments with ESLint

[Planeshifter]

Ref: stdlib-js/stdlib@dca9cf7

We already have lint rule jsdoc-no-tab, which checks JSDoc descriptions to ensure. Will should refactor this lint rule to check the entire comment instead and ensure no TAB indentation is used anywhere in the JSDoc comment.

Time estimate with AI: 45min.
Time estimate without AI: 1hr.

[Planeshifter]

PR-URL: stdlib-js/stdlib#5325

[Planeshifter]

Loom of initial pass (7m): https://www.loom.com/share/12297d6a5b7449abaafb87716b7289c9

[Planeshifter]

Time until PR was ready: 23min.

Time after initial PR until merged: 0min

[Planeshifter]

Notes: Cursor shined during this refactoring. Composer made all the changes immediately in one shot. The remaining couple of minutes I spent adding additional test fixtures to ensure that the lint rule was behaving as expected. Total time until I assumed PR was ready: 7min.

In the end, it took a little longer, but not by much: After pushing changes, I noticed that linting was failing. I located the problem being that JSDoc nested inside functions is getting extracted by our @stdlib/_tools/eslint/utils/find-jsdoc utility, such that we were getting suddenly lint failures due to the TABs to the left of the JSDoc asterisks, *. I added some logic to strip the leading TABs in order to get this to work (note: we probably should look into improving @stdlib/_tools/eslint/utils/find-jsdoc )