Bug/unity 1463 fix device id on frame

[MaxPalmer-UH]

Summary

Device IDs are not set correctly on Frame objects, particularly when handling playback of data via LeapCtrl, which will create new devices per playback.

Contributor Tasks

• Create or edit test cases here
• 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.

Test Cycle

Link to the test cycle here.

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.

[MaxPalmer-UH]

Sorry, accidentally branched off the raw frame ready branch.

[MattGrayUL]

I think this might actually draw attention to a larger issue

Conection.Frames has no idea about devices, and so is a stack of all frames, regardless of device. We then populate it with whichever frame is available

This means when interpolation is not enabled, the provided data can be from any active device, regardless of the device that should be used for the specific LeapServiceProvider