fix(output): exit simulation if output configuration is erroneous

[hoelger]

Description

Changes the error handling into the direction of "fail early and hard" when the output is not well configured. This might lead to bigger discussions in the group, but I think

Issue(s) related to this PR

• Resolves internal issue 977

Affected parts of the online documentation

No

Changes in the documentation required?

Definition of Done

Prerequisites

• You have read CONTRIBUTING.md carefully.
• You have signed the Contributor License Agreement.
• Your GitHub user id is linked with your Eclipse Account.

Required

• The title of this merge request follows the scheme type(scope): description (in the style of Conventional Commits)
• You have assigned a suitable label to this pull request (e.g., enhancement, or bugfix)
• origin/main has been merged into your Fork.
• Coding guidelines have been followed (see CONTRIBUTING.md).
• All checks on GitHub pass.
• All tests on Jenkins pass.

Requested (can be enforced by maintainers)

• New functionality is covered by unit tests or integration tests. Code coverage must not decrease.
• If a bug has been fixed, a new unit test has been written (beforehand) to prove misbehavior
• There are no new SpotBugs warnings.

Special notes to reviewer

[hoelger]

Todo: check that it is OK if there's no output_config.xml given, which should be possible. Does this exist in a test?

[kschrab]

Todo: check that it is OK if there's no output_config.xml given, which should be possible. Does this exist in a test?

Would it make sense then to have the output ambassador activated? What happens now if no output_config is given?

[hoelger]

Ah true, I didn't think of that option!

Currently we have a slightly misleading error if the file is missing but the output generator is enabled:

--------------------------------------------------------------------------------
 Stopping simulation due to a critical error:
	- RuntimeException: java.io.IOException: Invalid XML syntax
	- Root Cause: FileNotFoundException: C:\Users\geo27059\Documents\Code\mosaic-extended\test\scenarios\workshop-highway-vms\output\output_config.xml (The system cannot find the path specified)
 Please see the log files for details.
	- Log-Directory: logs\log-20250328-101815-workshop-highway-vms
--------------------------------------------------------------------------------
 MOSAIC will now shut down.
--------------------------------------------------------------------------------

I will think of a solution and propose one.

.... thinking of it: The root cause (second error) is very explicit. Maybe that's enough... lets see.