Add release notes for meshlet BVH culling

[SparkyPotato]

Objective

• To add release notes

Solution

• Write the release notes

Testing

• Read them

---

Showcase

(example screenshot of what should go in when we add images)

[atlv24]

Suggested change

	Speaking of GPU cost, the scene above renders in about 3.5 ms on the 4070, with ~3.1 ms being spent on the geometry render and ~0.4 ms on the material evaluation.
	Speaking of GPU cost, the scene above renders in about 3.5 ms on a 4070, with ~3.1 ms being spent on the geometry render and ~0.4 ms on the material evaluation.

[SparkyPotato]

I was referring to the 4070 + 1440p combo mentioned above

[JMS55]

Suggested change

	Bevy's virtual geometry has been greatly optimized with BVH-based culling, leading to almost true scene-complexity invariance on the GPU.
	Bevy's virtual geometry has been greatly optimized with BVH-based culling, making the cost of rendering nearly independent of scene geometry. (Then write something here about 120k vs 1 million instances).

[JMS55]

Suggested change

	This gets rid of the previous cluster limit that limited the world to 2^24 clusters (about 4 billion triangles).
	This also gets rid of the previous cluster limit that limited the world to 2^24 clusters (about 4 billion triangles).

[JMS55]

Suggested change

	There are now *no* hardcoded limits to scene size, only unique instance limits due to VRAM usage (since streaming is not yet implemented),
	and total instance limits due the current architecture requiring all instances to be uploaded to the GPU every frame.
	There are now *no* hardcoded limits to scene size. In practice you will only be limited by asset VRAM usage (since streaming is not yet implemented),
	and total instance count due the current code requiring all instances to be re-uploaded to the GPU every frame.

[JMS55]

I don't think this sentence would mean much to people not very familiar with the rendering code.

[JMS55]

Add something like "this is X times the triangle count, but only Y more GPU time"