Reflect derived traits on all components and resources about bevy

[blazepaws]

I went through all subcrates and fixed everything I could find. I consider this done.

[MrGVSV]

FYI, there was talk of deprecating reflect(Debug), so by adding this, you may be increasing future workload. Can we skip that one? Ping @MrGVSV

I'm on the fence about deprecating it. I agree that generally speaking, the reflection-based Debug impl should work for most cases. However, there are many cases where a custom Debug impl might be desired. And the PR to deprecate it (#11625) uses autoref specialization magic to automatically implement it.

I'd like to see benchmarks and/or a breakdown of performance, maintainability, and support implications before committing to that idea. Or at the very least, I'd like to know that Bevy is comfortable with utilizing these quasi-specialization hacks.

Until then, I think it's perfectly fine—and probably desirable—to add reflect(Debug) to types.

[janhohenheim]

FYI, there was talk of deprecating reflect(Debug), so by adding this, you may be increasing future workload. Can we skip that one? Ping @MrGVSV

Edit: leave it in, per reasoning below

[alice-i-cecile]

This should be done, but is easy to forget. When tackling this, please handle it one crate or so at a time: it's helpful to avoid merge conflicts and review burden.

[blazepaws]

I'm working on this but can only get started on Sunday, so no pull request just yet.

I'm also wondering if a lint could be written to remind people to do this on future components and resources.
I'll investigate that one when I'm done with this issue.

[janhohenheim]

@blazepaws much appreciated, thanks!