ESLint Config Migration: Object property names enclosed with quotes require no naming convention

[filmaj]

Summary

This is a PR that should be merged into #1024 and incrementally addresses #842.

This PR tweaks the naming convention rule such that object properties enclosed in quotes do not need to adhere to specific naming conventions. This is useful for things like specifying HTTP header names as properties on an object, since HTTP header names typically use a kabob-case naming convention (usually capitalized, too).

Impact

Before

✖ 765 problems (576 errors, 189 warnings)
  103 errors and 0 warnings potentially fixable with the `--fix` option.

After

✖ 761 problems (572 errors, 189 warnings)
  103 errors and 0 warnings potentially fixable with the `--fix` option.

Requirements (place an x in each [ ])

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[filmaj]

Hmm, it seems like this PR is no longer needed as the targeted rule passes now on the base PR. Well, great, I guess! Closing.