fix: 🐛 remove unnecessary transforms from worker

[thkruz]

This migrates both workers and the frontend from satellite.js to ootk for better TypeScript support and modernization for alpha 5. As I am the main contributor to satellite.js I can tell you with certainty that it will not be supported as we reach 6 digit satellites and sgp4-xp formats. I know we had a discussion about AGPL vs MIT. You can hold off merging this until I either update the license or write you an exception to it. I am looking at ways to split the core functions from the ones I have added and will happily leave the core ones under MIT.

[thkruz]

It is going to take me a few days, but I have all of the core orbital functions from ootk moved to a new library under MIT (ootk-core). That will give you all of the functionality of satellite.js plus the fixes I have made for alpha-5 (satellite number 100,000+) element sets and a lot of useful transforms - all under MIT. I will keep the more advanced math for initial orbit determination and other tasks common in commercial software under AGPL, but I don't imagine you ever needing any of that for this project.

I'll change the dependencies once the new library is on npm.

[ajmas]

No rush. I'm trying to balance things the best I can too.

[thkruz]

Ton of updates/fixes:

• Sun is in the correct location.
• Earth is rotated correctly.
• Scene is rotated have axis in correct direction.
• Satellites are in the correct location.
• Satellites position is update every frame using velocity.
• Orbits are in the correct location.
• ootk replaced with ootk-core (MIT License).
• All ECI and LLA math offloaded to ootk-core.
• satData and satCache arrays replaced with Satellite class arrays.
  • adds lots of built-in helper methods.
  • reduces back and forth with position worker.
  • consolidates parameters between space-track.org data and old satellite object.

I am using this project to determine what will be in ootk-core and to standardize terms like rightAscension vs raan, but I am confident you can proceed at this point (if you think it is ready). If there are any adjustments you'd like in the syntax of ootk-core just let me know, and if nothing is heard in the next few weeks I will mark it is officially version 1.

Let me know what you think.