feat: ScriptExecutionOrder component to control script execution order on entities

[CrushedPixel]

Summary

This PR adds a ScriptExecutionOrder component that, when added to entities with ScriptComponent,
specifies the order in which entities are iterated for script traversal.

I require control over script execution order as scripts should be able to build on top of each other's world changes
in a deterministic way.

Example usage:

fn spawn_scripts(mut commands: Commands) {
    commands.spawn((
        ScriptComponent::new(vec!["scripts/mod_a.lua"]),
        ScriptExecutionOrder(2), // runs after mod_b
    ));

    commands.spawn((
        ScriptComponent::new(vec!["scripts/mod_b.lua"]),
        ScriptExecutionOrder(1), // runs before mod_a
    ));
}

Caveats

• This system doesn't allow ordering of static script execution

Considerations

• If this approach is viable, I'll be happy to add some tests and benches

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
crates/bevy_mod_scripting_core/src/handler.rs	64% smaller
crates/bevy_mod_scripting_core/src/script.rs	0% smaller

[CrushedPixel]

Closing in favor of simply dispatching entity-specific events in order