Question: How should these crates be handled?

I took some notes as I went by adding a `crate` field to every asset:

```
Unreleased (AKA a crate with no crates.io release):
- bootleg_networking
- bevy_input_actionmap
- bevy_advanced_input
- prototype_bevy_sdl2
- bevy_shadertoy_wgsl
- bevy_miniquad
- bevy_prototype_css
- Bevy-WoW
- bevy_kajiya: Unreleased?
- bevy_dev_console: Crate name reserved, though.
- bevy_doryen: There's a different library with the same name that _is_ released...
- bevy_prototype_simple_net: Also archived.

Archived (on GitHub):
- bevy_rtc
- bevy_networking_turbulence
- physme
- spew
- ezinput
- bevy_tilemap
- bevy-discord-presence
- bevy_ldtk: Merged into bevy_retrograde.

Unmaintained (according to README):
- bevy_retrograde: No longer developed. Moved to Bones Framework, which is not a Bevy plugin.
- seldom_interop: No longer maintained. Merged into seldom_map_nav.
- bevy-orbit-controls: Unmaintained. Suggests using smooth-bevy-cameras instead.

Obsolete:
- seldom_fn_plugin: Almost obsolete.
- bevy_mod_ui_sprite: Obsolete?
- bevy_ui_borders: Obsolete?
- bevy_mod_ui_texture_atlas_image: Obsolete?

Wrong category:
- bevier: Tool, not a template.
- bevy-in-web-worker: Tool, not a crate.
- bevy-in-app: Tool, not a crate.
- autodefault: Not a "development tool", and not even a Bevy Asset technically, just a Rust library.

Multiple crates:
- blender_bevy_components_workflow
- naia
- avian
- bevy_rapier
- bevy_wasm
```

No files or tests are named. Start with the crate field notes in this issue and review the eight comments for an established policy; done means the listed assets have an agreed, consistent category and the asset metadata reflects that decision.

Written by the indexing model from the issue text.