ENH: adoption of the built-in python loggers instead of simple prints

[Gui-FernandesBR]

Is your feature request related to a problem? Please describe.

RocketPy doesn't offer a good way of tracking the execution steps when running a flight simulation.
There are some prints around the code, but they do not cover all the classes and do not look robust enough for a definitive solution as rocketpy wants to be.

Describe the solution you'd like

• Adopt the best practices from the built-in logging facility of Python. A basic guide is available here: https://docs.python.org/3/howto/logging.html#logging-basic-tutorial. Further investigation may be needed to understand how exactly this module works.
• Ensure that at least the core classes are supports log messages from logging.
• We should also allow for a log file generation to be accessed by the end of the execution.
• The Flight class could be the first one to receive this new feature.

Additional context

• I'm guessing this implementation would leverage the debugging process of rocketpy's simulations, saving valuable time for both devs and users.
• It is not a good idea to define log handlers inside the library, but it is totally OK to use loggers instead of prints so the final user can decide how to format or handle the loggers data.