utils package with updated CLI

[DynamicsCoder]

A suite of tools for aircraft trajectory and scenario generation, supporting both real ADS-B data processing and artificial track generation (random and from Google earth).

Addition -

1. Scenario report generation from config.json - will generate a markdown scenario overview with trajectories on map.
2. CLI to install scripts
3. Updated readme

[DynamicsCoder]

adding @effendi-aerosim comment for tracking the package

This looks like a great set of helpful processing tools. Instead of checking it in as an independent Python package folder, here are my initial thoughts about how it could be directly integrated into the main aerosim Python package.

• 1. These files could be added into the aerosim/src/aerosim/utils/ folder that currently just has a few utility helper functions. The README could either be added to the main aerosim package README or put as a README inside the utils/ subfolder with a link from the main README. I'm not sure how these package READMEs will end up being exposed to the user through the installed wheels though other than being on the PyPI site for the package once uploaded.
• 2. The aerosim CLI tool could be generalized to be the root CLI for the aerosim main package, as you already have it setup to be run as aerosim [command]. We would add to the command set the aerosim prereqs and aerosim install commands to run the install scripts and aerosim launch to run the launch scripts directly from the wheel.
• 3. The aerosim scenario part of the utils could be integrated to also utilize the aerosim-scenarios package that has some structure and utility functions set up to generate sim config JSON files from a broader scenario definition JSON format. Adding in the parts for generating the trajectories from ADSB, artificial maneuvers, and KML files would be useful here. The aerosim-scenarios structure is a bit stale and needs to be refreshed to match the latest sim config structure and features, but this might be a good opportunity to bring it back into a workflow through this utils scenario tooling.

@praveen-palanisamy What are your thoughts on this?