FEAT: Result visualization

[mberz]

Proposed changes

• Added a new API endpoint /simulations/<int:simulation_id>/visualization/<string:visualization_type> for retrieving visualization data, and registered the corresponding blueprint in app/blueprint.py.
• Implemented the visualization_service module, which generates and saves plot-ready JSON files (e.g., impulse response, spectrum, energy decay curve) after a simulation completes, and provides a method to retrieve them for visualization.
• Integrated the visualization data generation step into the simulation pipeline, so that visualization files are automatically created after a successful simulation run.
• Defined the VisualizationLineData Marshmallow schema for structuring the API response
• Added unit tests for the visualization service covering data generation, retrieval, and error handling, ensuring robustness of the new feature.
• Updated dependencies: pydantic and pyrato, required for the visualization service.

related to

• Impulse response visualization not useful for analysis frontend-v2#16
• Feat/impulse response visualization frontend-v2#192

Remarks

• The creation of the data is probably better done one demand, not only after a simulation finishes. This should be implemented separately after ENH: Define and harmonize data return types for simulation-methods CHORAS#56 has been implemented