Cherry-picks development -> stabilization

[jhanca-robotecai]

What does this PR do?

The development in the o3de-extras repository did not follow the agreement made for o3de, in which all code had been targetting the stabilization branch. Therefore, the vast majority of the fixes and features that were implemented after the split are not available in the stabilization branch. This PR cherry-picks the commits from the development branch.

The list of PRs that were cherry-picked from development to stabilization:

• #697 bugfix in ROS 2 Gem (controlling joints)
• #695 prefab update (update assetHint to match O3DE >=2310)
• #700 repo.json update
• #703 bugfixes ROS 2 related Gems (required O3DE version was incorrect)
• #704 feature: spawning entities with WGS84 coords in ROS 2 Gem
• #708 bugfix in ROS 2 Gem (in ROS 2 System Component)
• #712 fixes in documentation (spelling)
• #707 feature: modifications in ROS 2 Gem's clock design
• #715 bugfixes for ROS 2 sensor's configuration
• #724 bugfixes for ROS 2 Lidar sensor
• #720 small refactor in ROS 2 lidar sensor (storing data as quaternions instead of Euler angles)
• #733 feature: support to do MSAA Resolve in OpenXRVk
• #714 more improvements to #707
• #726 feature: display full name in ROS 2 Gem's component
• #738 feature: constructor with parameters to ROS 2 TopicConfiguration
• #731 removal of the obsolete documentation
• #723 fixes in ROS 2 project templates
• #734 feature: improvements in ROS 2 Gem's URDF/SDF importer

The list of PRs that were NOT cherry-picked from development to stabilization:

• #737 Lidar intensity feature that targets the next release (this PR is a partial implementation only)
• #716 Multi-device-resources fix that requires O3DE development

I am aware some features were cherry-picked alongside bug fixes, but there is enough time to fix any issues that can be brought up with this PR before the release.

We use #704, #707, #714, #726, and #738 extensively in projects for our clients; we believe this part is well-tested by us. #720, #733, and #726 are very small changes that should not bring any issues. The only large PR, #734, implements the features for Robot Importer that were recently discussed on Discord and that are valuable for the community, hence worth adding to the scope of this PR. Any problems in this code might result in importing the robot incorrectly (instead of skipping some parts of the import), but should not result in any crash.

How was this PR tested?

A sample project was built and run with no issues; diff between this branch and the development branch was analyzed.