Graduate Non Native Keyboard from experimental

[thalbern]

Describe the problem

NonNativeKeyboard class is rather long - here are a few thoughts on how we could split things up / make them more generic:

• moving the record button functionality and properties out of the class
• moving function buttons out, so you can iterate over a generic / flexible list of function buttons that can be plugged together in the editor
• min max scaling could be replaced by our scaling constraint (previously transformscalehandler) in a further refactor (as well as min / max distance -> move constraint)

These are just some initial thoughts I had when looking at the code - whoever grabs this task needs to do some investigation first :)

Additional context

related to #6687 #6688 #6689 This is a follow up task for the NonNativeKeyboard ported from HTK - PR #6492

[polar-kev]

The non native keyboard would need to be updated with the latest MRTK layout tools.

[IssueSyncBot]

We appreciate your feedback and thank you for reporting this issue.

Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.

Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.

Please note that MRTK3 was released in August 2023. It features an all new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visithttps://www.mixedrealitytoolkit.org.

Thank you for your continued support of the Mixed Reality Toolkit!