Use workspace inheritance to abstract some packages metadata

[ameknite]

Objective

• Abstract the package metadata in all the crates

Solution

Use workspace inheritance to define the next fields:

version.workspace = true
edition.workspace = true
homepage.workspace = true
repository.workspace = true
license.workspace = true
authors.workspace = true
readme.workspace = true
rust-version.workspace = true

I also added some keywords and categories, and included the macro repositories as members of the workspace.

[waywardmonkeys]

This might be a good time to start using workspace inheritance! It would also be useful for license, repository, and other fields.

[alice-i-cecile]

That's an excellent call. Can we do that here and update the title + description to match?

[mockersf]

Authors were removed in #2654

[alice-i-cecile]

Much nicer :) A bit annoying that we have to list "please we do actually want to use that" in all of the child crates, but if that's required there's nothing we can do.

[mockersf]

I don't think using workspace inheritance for metadata is that interesting, as it's very verbose and doesn't really solve a problem.

#6089 was doing pretty much that and was rejected.

[ameknite]

Just for context, I just did this PR because I wanted to have author data when listing all the dependency licenses with Cargo license. I found it strange that other crates have an author, but Bevy doesn't.

Example:
bevy_window: 0.12.0-dev, "Apache-2.0 OR MIT", by, "N/A"

instead of something like

tracing-core: 0.1.31, "MIT", by, "Tokio Contributors <team@tokio.rs>"

[ameknite]

@mockersf, I think that if there are problems with the version metadata, we can set it manually. However, I don't see any reason why we shouldn't use workspace inheritance for something like the repository field.