Add Per-Version Configuration Launch Settings

📋 Summary

Allow additional apps/versions to define their own configuration application path and configuration command-line parameters.

❗ Problem

LaunchBox games can have configuration launch settings, including a configuration application path and configuration command-line parameters.

However, when multiple versions of a game are kept under one entry using additional apps/versions, those versions do not appear to have their own separate configuration launch settings.

This can be limiting when different versions of the same game need different setup or configuration behavior.

💡 Proposal

Add optional configuration launch settings to additional apps/versions.

Each version should be able to define its own configuration application path and configuration command-line parameters, while falling back to the main game’s configuration settings when no version-specific values are set.

🧩 Use Cases

• Configure different versions of the same ScummVM game separately

• Use version-specific setup tools or launch options

• Keep AGI and SCI versions of a game under one tidy entry

• Avoid splitting versions into separate games just to support different configuration behavior

📦 Benefits

• Makes the versions feature more flexible

• Improves support for ScummVM and emulator edge cases

• Helps users keep cleaner libraries

• Reduces duplicate game entries

⚠️ Considerations

The UI should make it clear whether a version is using its own configuration settings or inheriting them from the main game. Existing per-version application command-line parameters should remain unchanged.