example `occlusion_culling` crashes: Buffer with conflicting usages

[mockersf]

Bevy version and features

• main since Upgrade to wgpu 28 #22265

[Optional] Relevant system information

macOS, Linux, Windows

What you did

cargo run --example occlusion_culling

What went wrong

ERROR wgpu::backend::wgpu_core: Handling wgpu errors as fatal by default

thread '<unnamed>' (15377447) panicked at /.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wgpu-28.0.0/src/backend/wgpu_core.rs:2631:18:
wgpu error: Validation Error

Caused by:
  In a CommandEncoder
    In a dispatch command, indirect:true
      Attempted to use Buffer with '' label with conflicting usages. Current usage BufferUses(STORAGE_READ_WRITE) and new usage BufferUses(INDIRECT). BufferUses(STORAGE_READ_WRITE) is an exclusive usage and cannot be used with any other usages within the usage scope (renderpass or compute dispatch).


note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic in system `bevy_render::renderer::render_system`!

[mockersf]

also broke caldera_hotel and bistro

[ChristopherBiscardi]

all the examples mentioned landed in the middle of the wgpu 28 upgrade, so likely just need api adjustments.

occlusion culling specifically seems like it is running into gfx-rs/wgpu#8399 (more context) which was not in the wgpu 28 changelog and seems like it fixed validation for something that wgpu 27 was not detecting