Env/flight axial aceleration

[hogatata]

Pull request type

• Code changes (bugfix, features)
• Code maintenance (refactoring, formatting, tests)

Checklist

• Tests for the changes have been added (if needed)
• All tests (pytest tests -m slow --runslow) have passed locally

Current behavior

Currently, the Flight class calculates various kinematic properties, but it does not explicitly expose the axial acceleration (acceleration along the rocket's longitudinal axis) as a direct property or method. Users have to calculate it manually from other components.

New behavior

This PR adds the calculation of the axial acceleration to the Flight class:

• Implemented axial_acceleration calculation.
• Added a corresponding unit test to verify the correctness of the values against expected physical behavior.

Breaking change

• Yes
• No

[Copilot]

Pull request overview

This PR aims to add axial acceleration calculation to the Flight class, which represents the acceleration along the rocket's longitudinal axis. However, the PR includes several unrelated changes that significantly expand its scope beyond the stated purpose.

Key Changes:

• Added axial_acceleration property to calculate acceleration along rocket's axis
• Added corresponding unit test using dot product verification
• Unexpectedly restored previously deprecated export methods (export_pressures, export_data, export_sensor_data, export_kml) with full implementations

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

File	Description
rocketpy/simulation/flight.py	Added axial_acceleration cached property; restored export methods that were previously moved to FlightDataExporter; removed self.apogee initialization; added json and simplekml imports; removed deprecated import
tests/unit/simulation/test_flight.py	Added parameterized test to verify axial_acceleration calculation against manual dot product computation at key flight times

[Gui-FernandesBR]

@hogatata are you still willing to work on this one? Tests are not passing, we need that fixed before starting our review

[hogatata]

I am still working on this. I will look into the errors and fix the failing tests as soon as possible. @Gui-FernandesBR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.78%. Comparing base (9cf3dd4) to head (202a69b).
⚠️ Report is 16 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #876      +/-   ##
===========================================
+ Coverage    80.27%   80.78%   +0.50%     
===========================================
  Files          104      107       +3     
  Lines        12769    13377     +608     
===========================================
+ Hits         10250    10806     +556     
- Misses        2519     2571      +52     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Gui-FernandesBR]

@hogatata is this PR ready for review again? Please mark it as ready for review, and solve all the comments above

[Gui-FernandesBR]

@hogatata please update the CHANGELOG.md file so we can approve and merge this PR.

Everything is looking good to me!

[hogatata]

@Gui-FernandesBR Done! I've updated the CHANGELOG.md file.

[Gui-FernandesBR]

LGTM