ENH: Support multiple export formats (CSV, JSON) in MonteCarlo class

[MateusStano]

Description

Following the progress made in #242 and #912, the MonteCarlo class currently relies primarily on .txt files for exporting and reloading simulation data. To increase interoperability with data analysis tools, I propose adding native support for .csv and .json formats directly within the class constructor and its file-handling logic.

Proposed Changes

1. Update MonteCarlo.__init__

Introduce an export_type parameter to allow users to specify the desired output format at initialization.

def __init__(
    self,
    filename,
    environment,
    rocket,
    flight,
    export_list=None,
    data_collector=None,
    export_type="txt"  # New parameter
):

• Supported types: "txt", "csv", "json".
• Behavior: The class should internalize this preference to determine how results are written to disk.

2. Standardize Export Logic

The implementation should ensure that the resulting files are consistent with the output currently generated by:

• export_results_to_csv()
• export_results_to_json()

3. Enhanced File Loading

When a filename is passed to the constructor that points to an existing file, the class should detect the extension and handle the data ingestion accordingly.

• If filename="results.csv", the class should parse it as a CSV.
• If filename="results.json", it should parse it as JSON.
• Maintain compatibility with existing .txt parsing.

[Gui-FernandesBR]

@MateusStano I don't understand why this issue was opened... Isn't this duplicated with #242?
Both #912 and #916 already try to solve it, is your proposal better in any way?

[MateusStano]

#912 and #916 only add a way to convert a MonteCarlo .txt to a .csv/.json. What I am suggesting here is:

1. Ability to import .csv and .json files via filename in the constructor, just as we do with .txt files currently
2. Ability to directly save outputs to .csv or .json (instead of having to save .txt and then call the converting function)