Scene JSON Backup Texture Embedding Changes in BabylonJS 5.0

The goal is to guarantee that a BabylonJS scene backup can be restored later without missing textures, even when the original texture files are not available.

Starting with version 5.0, SceneSerializer.Serialize omits base64‑encoded texture data by default, storing only texture URLs unless serializeTextures:true is explicitly set. Consequently, a backup created with the default settings depends on the accessibility of those URLs at load time, and loading multiple backups without disposing the previous scene may retain textures in GPU memory.

Should developers always enable serializeTextures:true for archival backups? How does the default change affect compatibility when upgrading projects from versions prior to 5.0? What is the recommended approach for disposing textures when loading successive backups to prevent GPU memory accumulation?