Remove content for removed features in 2027

[Gold856]

References to old Java tools, Labview, and other features removed in 2027 WPILib have been removed.

[sciencewhiz]

I won't have a chance to review in detail for a while. However, from a usability perspective (and SEO) I think I'd tend to prefer replacing things with stubs that point to replacement rather then a wholesale delete for 2027. Since it's a massive PR, and I've only been able to glance at it, I can't tell if that's what you've done.

See also #3041. I think it might be easier to reorganize first then delete if we're keeping stubs.

[Gold856]

It's just wholesale deletes with some minor spot fixes to remove references or use alternate ones, e.g. replacing Shuffleboard with Elastic. And yeah, I think a reorganization first might be easier. Although I'm not exactly sure if stubs would be particularly useful compared to just using rediraffe. I suppose if we use one stub for every major removed component like SmartDashboard and Shuffleboard, that'd be fine.

What I might do is move the spot fixes (the first commit) into a separate PR, which would allow us to be more aggressive in moving/deleting stuff. If you're going to review any part of this, review the first commit only. The rest is just wholesale deletes.

[sciencewhiz]

Although I'm not exactly sure if stubs would be particularly useful compared to just using rediraffe. I suppose if we use one stub for every major removed component like SmartDashboard and Shuffleboard, that'd be fine.

Right, that was what I was envisioning. Redirect any SmartDashboard article to the stub, and the stub can explain why it's no longer supported and link to alternates. I think that's a better user experience then redirecting any smartdashboard article to some other dashboard article without any explanation.

[Gold856]

I decided that I do want to do wholesale deletes and redirect to a stub. This mostly comes from the fact that since the reorg will necessitate that articles be moved around anyways, it will require all articles to find a new home, and a lot of articles that are currently up for removal (such as all the Java tools) are a mix of tutorial and reference, so we'd have to spend time to split them up, only to delete them. I think just deleting everything now, with all deletions pointing to one article listing all the removed features, and alternatives, will make things easier in the future.

[sciencewhiz]

files deleted should be removed from the ignore list in .github/workflows/inspector.json