fix(engine): improve drone stability and update platform validation schema

[RinZ27]

Summary

Refactored the drone navigation distance logic to use math.hypot for better numerical stability. While testing these changes, I noticed the CI was failing because the validation schema was missing several architectures and classes (like tricore, mips, automotive, mobile) that are actively used in the platforms/ directory.

Type of Change

• fix — Bug fix
• style — Formatting, no code change
• refactor — Code restructuring without behavior change
• ci — CI/CD pipeline changes

Changes

• Switched to math.hypot(dlat, dlon) in drone simulator to prevent precision issues.
• Updated VALID_ARCHES and VALID_CLASSES in eosim/core/schema.py to match real platform definitions.
• Removed duplicated simulator class definitions across multiple engine files.
• Applied project-wide linting fixes with ruff to address existing formatting errors.

Testing

• Unit tests pass (Verified with pytest)
• Integration tests pass
• Manual testing performed

Pre-Submission Checklist

• Code compiles without warnings
• All existing tests pass
• Commit messages follow convention
• Branch is rebased on latest master

Related Issues

None.

Screenshots / Logs

Local test run: 291 passed, 3 skipped in 1.41s

Additional Notes

The schema updates were necessary because the test_validate_all_real_platforms test was failing on every real platform due to the outdated allowed lists in schema.py. I also spent some time cleaning up the duplicated code blocks in the engine modules that I stumbled upon while debugging.

[srpatcha]

LGTM - math.hypot fix, schema updates, code dedup, and ruff cleanup all look good. Net code reduction.