Geometry collection marked as nanite has no fallback in cooked build when nanite is disabled

When geometry collection is set as nanite, there is no non-nanite render data cooked.
This means that there is no fallback if the cooked build uses r.nanite 0.
This used to work with some code workaround before UE5.3 because non-nanite render data could be generated at runtime in cooked builds. Since UE5.3 we expect all render data to come from the cooked data.

Open TN-ChaosFractures in QAGame

Select the GC_Column_01 (1B in the scene)

Open the Rest Collection asset

Check "Enable Nanite" on the asset settings

Look at the scene you will see the component, the shading will have changed due to the material not being well setup for nanite, but ignore that.

Now do console command: r.nanite 0

Observe that the column is no longer shown in non-nanite view