[RFC] Add strict config(s) for optioned rules

Problem

Some rules are simple:

• Don't require semantic changes (e.g. renaming a variable or changing declaration context)
• Always work well (e.g. trailing comma never hurts)
• Can be auto-fixed

However, some rules are problematic to apply:

• Require semantic changes
• Make readability worth in some cases
• Require significant manual changes (e.g. rewriting component to TS or renaming components)
• Can be auto-fixed, but with LARGE changes
• Or just too discussable

Examples:

• Shadowing:
  • https://github.com/nextcloud-libraries/eslint-config/pull/993
• Single-line arrays/objects:
  • https://github.com/nextcloud-libraries/eslint-config/pull/996
  • https://github.com/nextcloud-libraries/eslint-config/pull/997
• Top-level function style
  • https://github.com/nextcloud-libraries/eslint-config/issues/1003
• TS-first rules in a mixed environment
  • https://github.com/nextcloud-libraries/eslint-config/issues/980
  • https://github.com/nextcloud-libraries/eslint-config/pull/998
• Forced <script setup lang="ts">
• Forced <script> - <template> - <style> order in components
• Forced multi-word component naming
• Following Vue style guide to have first attribute on a new line (diff safe)

Proposal

Instead of hot discussions, local rule overrides and avoiding "painful" rules, we can provide them in a additional config

Start by reviewing the repository's existing ESLint configurations and the referenced rule discussions and pull requests. Define the additional configuration's scope and determine how the listed optioned rules should be separated from the existing configuration.