MNT: Refactor AeroSurfaces

[MateusStano]

Pull request type

• Code maintenance (refactoring, formatting, tests)

Checklist

• Lint (black rocketpy/ tests/) has passed locally
• All tests (pytest tests -m slow --runslow) have passed locally
• CHANGELOG.md has been updated (if relevant)

Changes

• Separate each AeroSurface class into a different file
• Made a few shared attributes part of the AeroSurface class

Breaking change

• Yes
• No

[codecov]

Codecov Report

Attention: Patch coverage is 80.60897% with 121 lines in your changes missing coverage. Please review.

Project coverage is 73.90%. Comparing base (fd4941c) to head (a749c01).
Report is 1 commits behind head on develop.

Files	Patch %	Lines
rocketpy/rocket/aero_surface/nose_cone.py	78.68%	39 Missing ⚠️
rocketpy/rocket/aero_surface/fins/fins.py	72.56%	31 Missing ⚠️
...ketpy/rocket/aero_surface/fins/trapezoidal_fins.py	80.00%	19 Missing ⚠️
rocketpy/rocket/aero_surface/tail.py	79.16%	15 Missing ⚠️
...cketpy/rocket/aero_surface/fins/elliptical_fins.py	87.03%	7 Missing ⚠️
rocketpy/rocket/aero_surface/air_brakes.py	85.71%	6 Missing ⚠️
rocketpy/rocket/aero_surface/rail_buttons.py	92.00%	2 Missing ⚠️
rocketpy/simulation/flight.py	50.00%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #634      +/-   ##
===========================================
- Coverage    73.92%   73.90%   -0.03%     
===========================================
  Files           70       79       +9     
  Lines        10032    10070      +38     
===========================================
+ Hits          7416     7442      +26     
- Misses        2616     2628      +12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Gui-FernandesBR]

Good job.

It will be much easier to add new AeroSurface now.

The flight.py file is the only one that warns me a bit. Please double check this file to ensure that you are not making any bad operation.

[Gui-FernandesBR]

This file deletion will probably create merge conflicts with the following PR: #597

[Gui-FernandesBR]

classes Fins and AeroSurface are abstract classes and therefore cannot be instantiated.
They are only exposed here if the user decides to create a new class based on them.
With that being said, I think we should avoid re-exposing them in the init files.

I don't want someone doing something like this:

from rocketpy import Fins

fins = Fins(...) # raises an error!!

An experienced user would still be able to import the class using its absolute path, like this:

from rocketpy.rocket.aero_surface.fins import Fins,

class NewFins(Fins):
    ...