Revert "Move visibility range checking from the CPU to the GPU if NoCpuCulling is specified. (#23115)

[kfc35]

This reverts commit ebfbc3f.

Objective

• A third PR that fixes Shadows disappear abruptly in visibility range example #23991

Solution

• Reverts the commit that causes the issue.
• This can be considered if the other solutions (Fix: Send CurrentView/ PointAndSpotLightShadowPrimaryCamera ’s world position via Immediates for gpu vis range culling #24197 & Fix: Use the auxiliary entity (associated camera view)’s position via ViewUniform for gpu visibility range culling  #24133) I’ve put up are not satisfactory, and we need more time to come up with a good solution (i.e. post 0.19 rc) that:
  • Implements PointLight and SpotLight shadow view behavior for gpu vis range culling that is agreed upon and looks good
  • Finalizes an appropriate way of sending this camera view world position data to the gpu (Immediates vs ViewUniformBuffer or other Uniform)
• Note: Meshes that are tagged with NoCpuCulling will not undergo cpu visibility range culling. That was implemented in a separate PR: https://github.com/bevyengine/bevy/pull/23107/changes#diff-fec33d34072b7b4be336571ceecf2c10fc9bafd8366c1b29531089b7e3ef621cL745-L748. If you want to use VisibilityRange functionality, you will still need to have CPU culling enabled for the mesh.

Testing

• cargo run --example visibility_range works normal now.
• Tested some other 3d examples make sure the pipeline is ok — atmosphere, pccm