Use PhantomData over a string for query error

[nicopap]

Objective

• Reduce space requirement of query errors.

Solution

• Use PhantomData over a &'static str
• Use the thiserror::Error macro to not manually implement Error and Display, bonus is it makes implementation more concise.
• Use a struct + enum instead of an enum with many branches that all have the same fields for QueryEntityError.

Note that it doesn't make sense to verify that the type is correct in the error message since it's guarenteed at compile time now.

What is left to do

• I adjusted the unit tests, but not the doc tests. Need to fix them.
• The same process should be repeated for QuerySingleError
• Remove the Vec<ComponentMismatch> from ErrorType, it is a huge blocker.
• It should be possible to replace the QueryEntityError<ErrInfo<Q, F>> by a QueryEntityError<Q, F>. You could define a type alias so that QueryEntityError<Q::ReadOnly, F> can be used as ReadQueryEntityError<Q, F>

Note that I spent an hour preparing this :)

[nicopap]

Suggested change

	impl<Q: WorldQuery, F: ReadOnlyWorldQuery> fmt::Debug for ErrorTypeInfo<Q, F> {
	impl<Q: WorldQuery, F: ReadOnlyWorldQuery> fmt::Display for ErrorTypeInfo<Q, F> {

I'm not exactly sure how this compiles. at line 1381

#[error("Error querying for {entity:?} in query {error_type_info}: {kind}")]

It calls the display implementation of ErrorTypeInfo, yet there is no such impl.

[nicopap]

@Selene-Amanita bump.

Note that the "what is left to do" section is not things I will do.

[Selene-Amanita]

I'm a bit busy with work this week but I promise I will look at it, thank you!

[nicopap]

@Selene-Amanita bump again.