Remove robotpy_extras from pyproject.toml

[virtuald]

This is a bit more work than it sounds, need to provide a good alternative mechanism that's easy to update.

[virtuald]

I think we could write a tool to help users add vendors to 'requires'.

A tool could ideally also check for updates, and detect if there were conflicts before offering them to users.

[gerth2]

No major complaint from a user-end, it's trivial to move it over in the toml file. It was always slightly confusing why there were two options.

Inject a comment by default that points at a doc page to how to update the field with common vendor dependencies might be a quick solution to the tool question. I'm not fully visualizing what value the tool has over just manually editing the file, and seeing the errors in robotpy if conflicts are added.

[TheTripleV]

I'm still a proponent of having a list to install "all". I like having a oneshot command to get everything under the sun

[virtuald]

I want to get rid of this, but pushing it to 2026.

[virtuald]

it does occur to me that there is something that robotpy-extras is useful for (but we should rename it to optional_components or something more obvious like that) -- namely, all of the optional wpilib pieces that we don't install by default (cscore, apriltag, etc). That's because they're all robotpy and are correlated together

I think all the vendor stuff should be removed from it and figure out a way to make 'requires' more useful.

[virtuald]

As part of this, we should inspect the requires lines and annoy users if they don't have some kind of specifier indicating version compatibility.