The versioning code was introduced in 4.1 release cycle when we were planning to release EEVEE next in 4.1. This means that the versioning was not applied to files created in 4.1 using EEVEE-Legacy and loaded into 4.2. Moving the code just before the EEVEE-Legacy removal make the versioning work as expected. There is no side effect inside the versioning code. Fix #123500