[Breaking Change][Refactor]--Remove all object manipulation functions from Simulator

[jturner65]

Motivation and Context

With the introduction of the RigidObjectManager, accessing object-related functionality via simulator became redundant, and was deprecated. This PR removes the object-related functionality from Simulator and Simulator bindings. It also moves trajectory-related functionality to PhysicsManager, while retaining the addTrajectory and removeTrajectory stubs in simulator.

Note : This is a breaking change to how objects are instanced and removed via python/python bindings. All examples and tutorials had been updated this past summer to the new mechanism, and deprecation warnings had been added to context help for all affected functional bindings, but this PR removes the deprecated functions completely from both c++ and bindings.

Note : The protocol for accessing objects has NOT changed in javascript. This will be updated in a subsequent PR.

How Has This Been Tested

All existing c++ and python tests pass

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.

[aclegg3]

Looks good to me. Nice to see this deprecated code removed.