`contiguous_iter` should be a compile error if not using table storage strategy

[BenjaminBrienen]

What problem does this solve or what need does it fill?

Using the wrong storage and attempting to use these methods results in a runtime error, which is suboptimal.

What solution would you like?

We can improve the API by making these iteration methods not return a result and instead gate the trait implementation on the GAT.

What alternative(s) have you considered?

N/A

Additional context

This is a new feature in 0.19, so if this is fixed in the RC, that would be cool.

[Jenya705]

It was considered (at least I did), but it is not very straightforward to do due to:

1. Dynamic queries (No information in compilation whatsoever and they reuse Query struct).
2. Lens queries (Query<(&NonTableComponent, &TableComponent)> (not dense) into QueryLens<&TableComponent> (not dense as well)).
3. Stable rust doesn't support const expressions in where clauses (Component::STORAGE_TYPE defines what storage strategy is used, a new trait for table components will have to be introduced).

(If we don't want to change the returning type of contiguous_iter then only the 3rd point stays but still I suppose it would require some refactoring not only in bevy_ecs but in other crates)