camelcase rule should ignore global variables by default

[hrax]

What rule do you want to change?
camelcase

Does this change cause the rule to produce more or fewer warnings?
Change should produce fewer warnings

How will the change be implemented? (New option, new default behavior, etc.)?
Change should be implemented as a new default behavior.

Please provide some example code that this change will affect:

/* globals g_form */
g_form.setValue("field", "value");

What does the rule currently do for this code?
Produces an error "Identifier 'g_form' is not in camel case." unless the variable is set as exception in camelcase rule allow property.

What will the rule do after it's changed?
In case the defined global variable is not present for the script, setting the variable as an exception in the camelcase rule would allow the developer to set said variable in the script and therefore avoid checks for camelcase. This is even more potentially harmful if you set up these variables as a regular expression.

Are you willing to submit a pull request to implement this change?
Not at the moment.

[platinumazure]

Hi @hrax, thanks for the issue.

I could support a new option for this, but not a default behavior change.

[hrax]

Hi @platinumazure, thank you for the reply.
New option sounds great as well.

[eslint-deprecated]

Unfortunately, it looks like there wasn't enough interest from the team
or community to implement this change. While we wish we'd be able to
accommodate everyone's requests, we do need to prioritize. We've found
that issues failing to reach accepted status after 21 days tend to
never be accepted, and as such, we close those issues.
This doesn't mean the idea isn't interesting or useful, just that it's
not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.