Add an example demonstrating how to load your assets sequentially to reduce memory usage on web platforms

## What problem does this solve or what need does it fill?

On WASM, memory cannot be reclaimed / freed. As a result, loading all of your assets up front in a loading-screen pattern will balloon your memory usage and it will never go back down. See https://github.com/bevyengine/bevy/issues/12057 for more context.

## What solution would you like?

Add an example demonstrating how to load assets one at a time, and then moving them onto the GPU using `RenderAssetUsage` once loaded.

Explain why this is useful for web.

## What alternative(s) have you considered?

We could make this the default behavior on wasm.

## Additional context

This came up when helping a commercial user debug performance issues on iOS.

Commencez par examiner l’approche de chargement des assets décrite dans cet issue et l’API RenderAssetUsage, puis lisez le contexte associé dans l’issue #12057. C’est terminé lorsqu’un exemple charge les assets séquentiellement, déplace chacun d’eux sur le GPU avec RenderAssetUsage et explique pourquoi cela réduit la mémoire non libérée sur les plateformes web.

Rédigé par le modèle d'indexation à partir du texte de l'issue.