Fix: handle computed properties in camelcase (fixes #11084)

[madbence]

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

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

Tell us about your environment

• ESLint Version: 5.9.0
• Node Version: 11.0.0
• npm Version: 6.4.1

What parser (default, Babel-ESLint, etc.) are you using? default

Please show your full configuration:

Configuration

camelcase: [2, {ignoreDestructuring: true}]

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

var { [category_id]: categoryId } = query;

What did you expect to happen?

Reported camelcase error for category_id.

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

No errors reported

What changes did you make? (Give an overview)

isInsideObjectPattern now stops at computed properties (as the computed property can be a simple expression, and node cannot be part of an ObjectPattern anymore).

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

I'd be happy to add more tests if you can think of more edge-cases.

[platinumazure]

Note to merger: This should be merged as an "Update" since this is a bugfix that adds more warnings.

[not-an-aardvark]

LGTM, thanks!

[not-an-aardvark]

@madbence It seems like there are some merge conflicts. Would you mind fixing those?

[madbence]

sure!

[madbence]

@not-an-aardvark is anything left i could do? 😸

[platinumazure]

LGTM, thanks!