Remove Wing area from Simple Landing builder defaults

[cmbenne3]

Summary

This PR addresses issue 980 and removes the set input default calls for the energy state landing group, which were unnecessary.
This simplifies the configurator and landing builder.

The landing component is updated to remove hardcoded density/unit conversion for calculation of Landing.INITIAL_VELOCITY. OpenMDAO now handles units and the dynamic density input is used.

Incorrect historical names removed from meta data for Landing.INITIAL_VELOCITY variable and replaced with the closest equivalent local and output variables from GASP and FLOPS. These mappings have no impact on functionality since neither ever appear in input files, but are included for completeness and to assist legacy code users with understanding the Aviary variable hierarchy.

Related Issues

• Resolves Landing group should not require Aircraft.Wing.AREA as an input in a model #980
• Resolves Incorrect assignment of legacy approach velocities to Mission.Landing.INITIAL_VELOCITY #1221

Backwards incompatibilities

Any custom scripts using the Landing class builder will fail.

FLOPS made the assumption that altitude = sea level for calculation of Landing.INITAL_VELOCITY (VAPP). This has now been updated to correctly use Dynamic.Atmosphere.DENSITY so will now differ from FLOPS values where landing altitude is greater than sea level.

VAPPR will no longer be converted from FLOPS input files with the fortran_to_aviary() function (however Aviary wasn't correctly interpreting this conversion anyway)

AI Usage

AI was used for assistance with changes to compute_partials() for the landing component.

[jkirk5]

Use of val here doesn't actually do anything and will be removed soon (see #1196, #1206). You'll need to update the test to directly set that value to get matching results instead

[cmbenne3]

Resolved - val removed from add_aviary_input call. We use set_input_defaults() in the tests instead