Split Resource and Component Access

[re0312]

Objective

• fix Incorrect handling of EntityRef/Mut Queries + Resources resulting in false conflicts #13139
• Currently, Bevy's system access does not differentiate between components and resources. This limitation can potentially lead to incorrect conflict detection in certain scenarios

Solution

• Added a resource access in SystemMeta

[hymm]

Note that this method will double the memory used for access, since resources and components share the same id space. But that would get fixed if #14385 gets merged.

[cBournhonesque]

Very nice!
Do you think an alternative approach of introducing read_all_components/write_all_components on top of read_all/write_all would work?

[re0312]

Very nice! Do you think an alternative approach of introducing read_all_components/write_all_components on top of read_all/write_all would work?

it appears to be a better solution than this pr.

[alice-i-cecile]

Do you think an alternative approach of introducing read_all_components/write_all_components on top of read_all/write_all would work?

This is my preferred approach here I think.

[cBournhonesque]

Very nice! Do you think an alternative approach of introducing read_all_components/write_all_components on top of read_all/write_all would work?

I'm not sure what I suggested is possible actually. Because then you would also need to be able to track if an access has any_read_component or any_write_component

[cBournhonesque]

Very nice! Do you think an alternative approach of introducing read_all_components/write_all_components on top of read_all/write_all would work?

I'm not sure what I suggested is possible actually. Because then you would also need to be able to track if an access has any_read_component or any_write_component

Actually I have a working version here: #14561

[alice-i-cecile]

Closing in favor of #14561.