Feature request: Publish config schema

[JP-Ellis]

Motivation

To help IDEs validate .config/nextest.toml files, highlighting errors while the file is being modified, instead of discovering issues later.

Proposal

Proposal is in two parts:

1. To make available on GitHub a schema for .config/nextest.toml. For example, much like the way committed have done this with config.schema.json.
2. (optional) To publish the schema to SchemaStore

Alternatives

There aren't really alternatives, save of having someone else create and maintain the schema.

Additional context

No response

[sunshowers]

Thanks. I actually looked at this a while ago but immediately ran into a bug in taplo (the library underlying Even Better TOML in VSCode), for which I submitted a PR: tamasfe/taplo#644

The failure mode of taplo crashing that is so bad that we added schema support today, VSCode users would actually have a worse experience than no schema at all.

With the way I'm making schemas (autogenerating them via schemars) there didn't seem to be an easy workaround. astral-sh/ruff#15992 works around this through writing some schemas by hand, but nextest's config is quite large and we'd have to write several schemas by hand. I was hoping that my PR to taplo (for what is a pretty clear bug) would have been taken by now, but the project unfortunately seems inactive.

So unfortunately we're at a bit of an impasse.

edit: Oh looks like the project is now active. I've pinged the person making the most recent commits since my PR has been lying untouched for a while. Hopefully it lands soon.