Update to dynamic UI and correct height functions on all pawns

[CesiumBen]

Summary

With the implementation of earth view in the main level I noticed two regressions.

• The correct height function on most of the pawns compared Z height values of the terrain and the pawn. This doesn't work when far from the world origin, so an update was made to compare the height returned from the cesium geo reference component's "Transform Unreal to Longitude, Latitude, Height". The issue before was being stuck under the terrain with no ability to move. Updated Blueprint
• The Dynamic UI doesn't orient itself properly when far from the georeference because the kismet "LookAt" function only considers the world up (non applicable when across the globe). So instead it implements the pawn's up which happens to be aligned with the globe, and when it isn't the widget is always legible. Updated Blueprint

Examples below taken from main level, after flying from Himalayas to NYC.

Before

After

Author checklist

• Tutorial for Fix
• Has the new tutorial been integrated into the main level? Yes
• Has a new section of the readme been added for this tutorial? N/A
• Have you done a full self-review of the code and blueprints? Yes
• Have you tagged a primary reviewer? Yes
• Are there any remaining tasks to do or blocking questions to answer before we can merge this? No

Testing plan

Test the main level:

• Teleporting should not send you under the terrain (should constantly correct as LOD increases)
• Dynamic UI should be oriented up all across the globe.

Reminders for reviewers

Thank you for taking the time to review this PR. By approving a PR you are taking as much responsibility for these changes as the author. Please keep these points in mind throughout the review process:

• Review and run all parts of the test plan on this branch and verify it matches expectations.
• Review the code and make sure you do not have any remaining questions or concerns. You should understand why this code change fixes the issue and agree that it's the best approach to doing so.
• Review the automated tests and make sure there are no missing tests or edge cases.
• When you feel this is ready bump it to a second reviewer or merge.

[xuelongmu]

Thanks Ben, this looks good to me.