fix: update astUtils.isDirectiveComment with globals and exported

[mdjermanovic]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[x] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

Tell us about your environment:

• ESLint Version: v8.13.0
• Node Version: 16.14.0
• npm Version: 8.3.1

What parser (default, @babel/eslint-parser, @typescript-eslint/parser, etc.) are you using?

default

Please show your full configuration:

Configuration

module.exports = {
    parserOptions: {
        ecmaVersion: 2015
    }
};

What did you do? Please include the actual source code causing the issue.

Online Demo

/*eslint no-inline-comments: "error" */

foo(); /* global foo */
  
bar(); /* globals bar */

var baz; /* exported baz */

What did you expect to happen?

No errors because this rule ignores eslint directives.

What actually happened? Please include the actual, raw output from ESLint.

/* global */ comment is allowed as expected, but /* globals */ and /* exported */ are disallowed.

  5:8   error  Unexpected comment inline with code  no-inline-comments
  7:10  error  Unexpected comment inline with code  no-inline-comments

✖ 2 problems (2 errors, 0 warnings)

What changes did you make? (Give an overview)

Fixed astUtils.isDirectiveComment to treat /* globals ... */ and /* exported ... */ as directives.

Is there anything you'd like reviewers to focus on?

• We noticed and fixed this bug in Breaking: allow all directives in line comments (fixes #14575) #14656, but that change was reverted in Revert "allow all directives in line comments" (fixes #14960) #14973.
• astUtils.isDirectiveComment is used only in no-inline-comments and no-warning-comments. In both rules this change can produce only fewer warnings.

[nzakas]

LGTM

[nzakas]

@mdjermanovic you’re not using a different email on this commit are you? EasyCLA looks unhappy.

[mdjermanovic]

@mdjermanovic you’re not using a different email on this commit are you? EasyCLA looks unhappy.

I used the same email. This happens sometimes with EasyCLA, I'll try close-reopen.

[mdjermanovic]

All checks are green now.