Mute non-local definition warnings in bevy_reflect

[stepancheg]

Objective

cargo check -p bevy_reflect

outputs a lot of warnings like:

warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
   --> crates/bevy_reflect/src/impls/std.rs:223:13
    |
223 |               impl_type_path!($ty);
    |               ^-------------------
    |               |
    |               `TypePath` is not local
    |               move the `impl` block outside of this constant `_` and up 2 bodies
...
346 | / impl_reflect_for_atomic!(
347 | |     ::core::sync::atomic::AtomicIsize,
    | |     --------------------------------- `AtomicIsize` is not local
348 | |     ::core::sync::atomic::Ordering::SeqCst
349 | | );
    | |_- in this macro invocation
    |
    = note: the macro `impl_type_path` defines the non-local `impl`, and may need to be changed
    = note: the macro `impl_type_path` may come from an old version of the `bevy_reflect_derive` crate, try updating your dependency with `cargo update -p bevy_reflect_derive`
    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
    = note: `#[warn(non_local_definitions)]` on by default
    = note: this warning originates in the macro `impl_type_path` which comes from the expansion of the macro `impl_reflect_for_atomic` (in Nightly builds, run with -Z macro-backtrace for more info)

Solution

Move impl_type_path! into global scope. Warnings no longer pop up.

Testing

CI

[stepancheg]

Also moved impl_full_reflect! call because otherwise I don't know how deal with mentioned rustfmt bug: it seems to ignore #[rustfmt::skip] instruction after my change and increases indentation.

[MrGVSV]

Note: this seems to be a nightly-only issue. Running cargo check -p bevy_reflect works fine on stable, but gives the warning when running cargo +nightly check -p bevy_reflect.

[MrGVSV]

This feels like a bug on Rust's end tbh. I don't see why a nested const block would cause this issue.

But the changes do seem to fix it regardless, so approving!