Port NASSP to OpenOrbiter

[CaptainSwag101]

For the future of NASSP's development, I think it would be wise to start planning to build for OpenOrbiter, since it has several bugfixes and other improvements that may make development easier. Here are what needs to be done to make this happen:

• Fix building with OpenOrbiter's SDK
• Switch from OrbiterSound to XRSound
• Fix remaining XRSound bugs (specific sounds like non-RCS engines were originally handled directly by OrbiterSound, and their functionality will either need to be moved to XRSound or done directly in NASSP now.)
• Fix certain D3D9Client issues, such as the EMS scroll texture causing crashes in the 3D VC, and the Floodlights not working
• Fix non-looping sounds like switches etc. not working if a user loads into a scenario starting with the 3D VC, right now those sounds don't work until switching to the 2D cockpit at least once per scenario load.
• Fix the 32-bit moons of Mars, Uranus, and Neptune causing corruption and destroying vessel orbits (remove them from our configs)
• Any other bugs found after the time of writing.

[ThymoNL]

I have seen patches by @TheGondos that add CMake support to NASSP. Those will also be a big help to making NASSP's development future proof.