Fix: quote-props shouldn't report object pattern properties

[mdjermanovic]

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

[X] Bug fix

Tell us about your environment

• ESLint Version: 6.1.0
• Node Version: 10.16.0
• npm Version: 6.9.0

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

default

Please show your full configuration:

Configuration

module.exports = {
  parserOptions: {
    ecmaVersion: 6,
  },
};

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

/*eslint quote-props: ["error", "always"]*/
({'a': foo, b: bar} = baz)

/*eslint quote-props: ["error", "as-needed"]*/
({'a': foo, b: bar} = baz)

/*eslint quote-props: ["error", "consistent"]*/
({'a': foo, b: bar} = baz)

/*eslint quote-props: ["error", "consistent-as-needed"]*/
({'a': foo, b: bar} = baz)

What did you expect to happen?

No warnings. By the documentation for this rule it targets object literals, these are object patterns.
Also, there are no test cases with patterns.

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

2 warnings, for always and as-needed.

No warnings for consistent and consistent-as-needed.

What changes did you make? (Give an overview)

Skip the check if the Property is not a property of an ObjectExpression.

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

I guess this should be treated as a bug rather than as an undocumented behavior because it doesn't work well - some options report warnings, some not.

[kaicataldo]

@mdjermanovic How would you like to proceed with this? Is this a WIP?

[mdjermanovic]

Closing this for the same reasons as #12047.

Further analysis in #12048