Render optional bevy_dev_tools

[Zeophlite]

Objective

• Fixes bevy_remote pulls in Bevy's rendering #24617

Solution

• Feature flagging the rendering crates
  • bevy_dev_tools has a render feature
  • bevy and bevy_internal have render_dev_tools feature that enables the above
• Split easy_camera out of easy_screenshot in bevy_dev_tools

Testing

• CI and various examples and build combinations

[hymm]

I ran cargo tree -p bevy_remote --no-default-features and cargo tree -p bevy_dev_tools and confirmed bevy_render is no longer being pulled in. I think this is an ok solution in the short term, so I'm approving.

In the long term, the stuff that is not rendering related feels like a repeat of bevy_utils a bit. For non rendering tools, we've got: a CI tool, merging 3d meshes, logging for pointer events, , logging for state transitions, schedule info, and some backend features for the inspector. It's tempting to split the crate into 2 with rendering vs non rendering features, but it might be better to wait and see. I expect the editor dev will make it more clear what the splits should be.