On grit plugin rule naming, scoping, and ignores

[cdaringe]

Problem statements

1. No way to name a rule in a .grit plugin
2. No way to apply the plugin to targeted sources with overrides
   1. i wanted to enable it for src/** but disable it from test/**

Context

Plugins get annotated in editor as biome(plugin), so I cannot apply a biome-ignore to violations. I see that the plugin has only grit_query in the struct. Would be nice to be able to reference this as noTypeAssertion or similar in my config!

My motivating context was building this rule today, noTypeAssertion:

language js(typescript)

`$value as $type` as $expr where {
  // Allow: as const, as unknown, as keyof ...
  !$expr <: or {
    `$_ as const`,
    `$_ as unknown`,
    `$_ as keyof $_`
  },
  register_diagnostic(
    span=$expr,
    severity="error",
    message="Type assertions (as) are not allowed. Use proper typing or type guards instead. Allowed: 'as const', 'as unknown', 'as keyof ...'"
  )
}

[ronyclau]

Biome seems to use the file name of the grit plugin as the rule name.

For example, if your grit plugin is named noTypeAssertion.grit, you should be able to suppress the error with

// biome-ignore lint/plugin/noTypeAssertion: some justification for the suppression

[cdaringe]

hmmm ill check again. The vscode extension didnt show as much but its worth another pass