Update the LeapC client libraries and continue to support older Android XR clients using an older LeapC client.

[MaxPalmer-UH]

Summary

Updates the LeapC client libraries to 7.4.X, adding an iOS client too. Because the newest Android client no longer supports binding to a service (and changes permissions - e.g. camera permissions), we bundle two clients (one with a LeapCLegacy name), switching which is in use based on whether Android and XR/VR are being used or not.

Newer Android clients expect to read the device firmware version when obtaining DeviceInfo - assuming they connect to a recent service. This field has been added and set to unknown if the service is older.

Note, testing with Quest 3 and service version 6.20 appears to show hand tracking is broken. A Pico + Leap 2 showed signs of life with LeapC.

In future w.b.n. to get a 16 byte aligned 6.2 client.

Contributor Tasks

• Add a CHANGELOG entry for this change.
• Ensure documentation requirements are met e.g., public API is commented.
• Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.

Reviewer Tasks

• Code reviewed.
• Non-code assets e.g. Unity assets/scenes reviewed.
• All tests must be ran and cover all scenarios (If not, add new tests to the cycle and run them).
• Documentation has been reviewed.
• Approve with a comment of any additional tests run or any observations.

Related JIRA Issues

If this MR closes any JIRA issues list them below in the form Closes PROJECT-#

Pull Request Templates

Switch template by going to preview and clicking the link - note it will not work if you've made any changes to the description.

• default.md - for contributions to stable packages.
• release.md - for release merge requests.

You are currently using: default.md

Note: these links work by overwriting query parameters of the current url. If the current url contains any you may want to amend the url with &template=name.md instead of using the link. See query parameter docs for more information.

[rblenkinsopp]

This looks good, my main questions are:

• Do we want to be including the HandTrackingServer.framework? This is needed to embed the tracking server, but we don't currently include the bindings for it, and this is normally done in the server part of the app at the moment? I'd almost be tempted to do this as a seperate package?

• Looks like Git LFS might be doing some strange behaviour, can you check the filters are correct and all files you expect to be LFS are?