[WIP] Robotics Coordinate System Migration

[aclegg3]

Motivation and Context

This PR represents a prototype of converting the default Habitat coordinate system to robotics conventions (Z-up, X-forward).

To make this work several systems needed to be changed:

• PathFinder: Recast Navigation is hard-coded to a local coordinate system with Y-up. To accommodate this requirement, we convert points between the coordinate systems in the wrapper layer. Part of this refactor is also to remove Eigen from the wrapper layer in preparation for parallel refactor (--[BE] Remove Eigen dependency Part 1 #2301).
• CoordinateFrame and ESP_UP/ESP_FRONT logic and defaults changed to fix a bug and correctly represent the new defaults.
• gravity vector is now -Z in the default config
• All configs for stages and objects should correctly represent the local up and front vectors in their own local asset coordindate system. This is now correctly converted to the new coordinate system.
• All Habitat custom URDFs previously had a default 1.56 radian rotation around X in the rpy. These should now be removed. Default URDF coordinate system will import correctly now.
• Added some test axis assets for debugging

TODO:

• needs many adaptations in the code where Y-up is hardcoded.
• needs many changes in the asset configs we host

How Has This Been Tested

Added examples/coordinate_system.py to test this migration.

• Changed hab_spot_arm.urdf to remove the base rotation rpy
• Changed the stage_config.json to correctly identify the local up and front.
• Apply a rotation to the camera (default cameras are in graphics convention with Y-up and need to be rotated).

Example. Note the colored axis (RGB == XYZ) indicating that we're now in robotics conventions!:

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have completed my CLA (see CONTRIBUTING)
• I have added tests to cover my changes.
• All new and existing tests passed.

[meta-cla]

Hi @aclegg3!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!