Change orthographic projection near default to -1000

[lkolbly]

Objective

Fix an issue where Camera2dBundle and OrthographicProjection have different defaults for the projection's near value. This causes confusion when a user starts with:

commands.spawn(Camera2dBundle {
   ..default()
});

and decides they need to modify just one field of the projection:

commands.spawn(Camera2dBundle {
   projection: OrthographicProjection {
      scaling_mode: my_scaling_mode,
      ..default()
   },
   ..default()
});

Since the user never mentioned the near field, it is surprising that the near field changes (from -1000. to 0.).

This issue was the inspiration for #11115.

Fixes #12267

Solution

This behaviour was introduced in #9310, which changed Camera2dBundle::default() to cover the region z=-1000. to z=1000. (so that sprites with negative Z are visible) and place the camera at the origin. This PR changes OrthographicProjection to have the same defaults as Camera2dBundle.

At the time, Camera2dBundle::new_with_far was not touched, since that would be a breaking change for that function, since that function is fairly explicit about the near/far range. This PR keeps near=0 in that function.

---

Changelog

• Changed default value for near plane for OrthographicProjection.

[lkolbly]

The CI failures seem unrelated to this change? It's complaining about:

error: field `0` is never read
   --> crates/bevy_asset/src/server/loaders.rs:311:14
     |
311 |     struct A(usize);
    |            - ^^^^^
    |            |
    |            field in this struct

[alice-i-cecile]

Yep, those are unrelated. See #12620.

[alice-i-cecile]

Solved by #15073 instead.