Fix: Send CurrentView/ an ExtractedCamera’s world position via immediates for gpu vis range culling

[kfc35]

Objective

• Also fixes Shadows disappear abruptly in visibility range example #23991
• (Better?) Alternate to Fix: Use auxiliary entity (reg view camera) for gpu visibility range culling if defined #24133 . Decisions made can be mixed and matched between the two, just let me know
• @JMS55 took a look and suggested using Immediates to avoid bloating ViewUniforms. There was also a concern about using RetainedViewEntity to pass information about what camera to use along. This is that alternate implementation path.

Solution

• Rely on the CurrentView (which either stores the current user camera OR the point/spot shadow camera) mechanism to get the current view’s world position. Use this for gpu vis range culling. This is the codepath directional light shadow views will take.
• For Point/Spot shadow cameras (aka RootNonCameraViews), a marker component has been added to denote the camera to use: PointAndSpotLightShadowPrimaryCamera. There must only be one camera with this component. This camera’s position is used for gpu vis range culling.
  • This component could probably be expanded later in functionality if desired, but I just went with what’s simplest.
  • If we don’t want to have this component, we can revert
    ac87f8e and return back to just querying for extracted cameras and taking the first one returned by the query.

Note

Copying this comment from @JMS55:
With this PR, we lose out on PreprocessingOnly support for WebGPU, until immediates are added to the spec and wgpu supports it.

Testing

• cargo run --example visibility_range -- --no-cpu-culling works with a directional light as desired
• I updated the light in the visibility_range example to be a Spot or PointLight like so:

SpotLight {
            intensity: 1_000_000_000.0, // lumens
            range: 110.0,
            color: Color::WHITE,
            shadow_maps_enabled: true,
            radius: 10.0,
            ..default()
        },
        Transform::from_rotation(Quat::from_array([
            0.6539259,
            -0.34646285,
            0.36505926,
            -0.5648683,
        ]))
        .with_translation(vec3(57.693, 34.334, -6.422)),

And added the PointAndSpotLightShadowPrimaryCamera to the Camera3d in the example, and then ran the example. The shadows of spot and point lights also look normal.

[JMS55]

Note: With this PR, we lose out on PreprocessingOnly support for WebGPU, until immediates are added to the spec and wgpu supports it.

[kfc35]

I will add a marker component for the camera to use for gpu vis culling spot and point lights shadows, that should be ready to review in a few hours

[github-actions]

Your PR caused a change in the graphical output of an example or rendering test. This might be intentional, but it could also mean that something broke!
You can review it at https://pixel-eagle.com/project/B04F67C0-C054-4A6F-92EC-F599FEC2FD1D?filter=PR-24197

If it's expected, please add the M-Deliberate-Rendering-Change label.

If this change seems unrelated to your PR, you can consider updating your PR to target the latest main branch, either by rebasing or merging main into it.