D3D12 Warnings #820/#821 spam output

## Bevy version

`bevy = { version = "0.10" }`

## \[Optional\] Relevant system information

```ignore
AdapterInfo { name: "NVIDIA GeForce RTX 3080", vendor: 4318, device: 8710, device_type: DiscreteGpu, driver: "", driver_info: "", backend: Dx12 }
```

## What you did

Running the below simple sample in Visual Studio Code with the console mode set to `internalConsole` and the environment variable `WGPU_BACKEND` set to `dx12`.

```
use bevy::prelude::*;

fn spawn_camera(mut commands: Commands) {
commands.spawn((
Camera3dBundle {
..Default::default()
}
));
}

fn main() {
App::new()
.add_plugins(DefaultPlugins)
.add_startup_system(spawn_camera)
.run();
}
```

## What went wrong

This results in the debug console being spammed with the following two warnings on my machine:

```
D3D12 WARNING: ID3D12CommandList::ClearDepthStencilView: The application did not pass any clear value to resource creation. The clear operation is typically slower as a result; but will still clear to the desired value. [ EXECUTION WARNING #821: CLEARDEPTHSTENCILVIEW_MISMATCHINGCLEARVALUE]
D3D12 WARNING: ID3D12CommandList::ClearRenderTargetView: The application did not pass any clear value to resource creation. The clear operation is typically slower as a result; but will still clear to the desired value. [ EXECUTION WARNING #820: CLEARRENDERTARGETVIEW_MISMATCHINGCLEARVALUE]
```

## Additional information

Other output modes which might intercept the output, like `integratedTerminal`, do not show this.

Start by running the provided minimal Rust sample in Visual Studio Code with WGPU_BACKEND set to dx12 and console mode set to internalConsole. Compare the output with integratedTerminal, then trace the D3D12 rendering path responsible for the two clear-operation warnings. Done means the sample runs without repeated warnings in the affected output mode while retaining the expected rendering behavior.

Written by the indexing model from the issue text.