--headless --import does not work as expected if localization data is present

### Tested versions

- Reproducible in 4.2.2.stable.official

### System information

macOS 14.6.1 - GLES3 (Compatibility) - Apple M1 - Apple M1 (8 Threads)

### Issue description

When using --headless --import with a project that has localization files connected (.en.translation), a single run is not sufficient to import all assets. A second, subsequent run with the same (--headless --import) parameters is required. I suspect the presence of localization causes the initial import to fail or early-out, so the second run can progress further until complete. This could be related to the number of localization files, I only tested with none and 1.

### Steps to reproduce

Create any Godot project. Add some resources like textures, so you can see them when you run your project.
Add a localization file
Clear all .godot folders
Run with --headless --import
Run directly and notice the textures are missing

Clear all .godot folders
Run with --headless --import
Run with --headless --import a second time
Run directly and notice the textures are present

Clear all .godot folders
Remove the localization files
Run with --headless --import
Run directly and notice the textures are present

### Minimal reproduction project (MRP)

[GodotImportTest.zip](https://github.com/user-attachments/files/17284237/GodotImportTest.zip)

Start with the attached GodotImportTest.zip reproduction project. Run the documented --headless --import sequence with and without the localization file, comparing whether one or two runs are needed before textures appear. Trace the localization and asset-import startup behavior; done means a single import run produces the same complete result without requiring a second run.

Written by the indexing model from the issue text.