Rule Proposal: vue/no-restricted-component-names

[qmhc]

Please describe what the rule should do:

Restrict some component names via a list of pattern.

What category should the rule belong to?

[ ] Enforces code style (layout)
[x] Warns about a potential error (problem)
[ ] Suggests an alternate way of doing something (suggestion)
[ ] Other (please specify:)

Provide 2-3 code examples that this rule should warn about:

Options:

{
  "vue/no-restricted-component-names": ["error", "Foo", "/^Baz(One|Two)/"]
}

<script>
<!-- ✗ BAD -->
export default {
  name: 'Foo'
}

<!-- ✗ BAD -->
export default {
  name: 'BazTwo'
}

<!-- ✓ GOOD-->
export default {
  name: 'Allow'
}
</script>

Additional context

Related #2180 (comment).

[ItMaga]

I think there can be cases when we need more detailed options, for example, when the team has some convention for suggestions or a custom error message. What do you think about this?

As a variant:

string[]
// or
{
  pattern: "string or regex",
  suggestion: "string", // optional
  message: "string" // optional
 }

[FloEdelmann]

I'm also fine with those options. However, if someone wants to implement this, adding only the string (or pattern) options is also sufficient.