Delete unused branches from this repo

[MarijnS95]

Seems we're releasing 0.4.1 straight from main so the v0.4 "stable backports" branch is off-track and should best be omitted. Same for v0.3 which is unused. Then there are some feature branches remaining which might be moved to user forks as well.

Also cannot find .cargo_vcs_info.json in 0.4.0 to validate that the tag is placed correctly.

[rib]

Ah, yeah I forgot I created a v0.4 branch.

We can merge main or release-0.4.1 back into v0.4 to maintain it. While we haven't got to the point of needing breaking changes the v0.4 branch isn't yet for back porting as such, it was just intended to be a branch that could be tracked in case you wanted a git branch that would follow 0.4.x releases and (potentially) back ported changes. That was the intent for the v0.3 branch too.

I've removed the openxr-cube-renderer and bevy-enabling branches, and just left the ime-support branch which is being referenced in an open issue atm.

I think I used --allow-dirty with the 0.4.0 release but not the 0.4.1 release and so cargo wouldn't have generated the .cargo_vcs_info.json file. This was a bit sloppy of me and I'm not planning to use --allow-dirty with future releases. (At the time I had a docs/MAINTAINERS.md file in the repo that wasn't being tracked in git to remind me of a few things while it was a faff dealing with the examples at the time, before the Winit backend was updated)

[MarijnS95]

I'd create that backports branch as soon as it's necessary, i.e. as soon as you start merging breaking changes to main so that we don't have to keep in mind to keep it up to date. Especially if there's no divergence from the main branch prior to that point (implied by releasing 0.4.1 straight from main).

Looks like we won't do any v0.3 releases though, unless you intend to keep the backported history there?

Indeed --allow-dirty also caused a bunch of your local files to be included in the crate source: https://docs.rs/crate/android-activity/0.4.0/source/. Nothing big/bad/major though.