Add support for visionOS

[freakboy3742]

Refs #50.
Fixes #49.

This is the code contributed by @johnzhou721, but with some additional consistency tweaks; as the PR for #50 was created from a main branch, it wasn't possible to commit directly to that branch.

PR Checklist:

• All new features have been tested
• All new features have been documented
• I have read the CONTRIBUTING.md file
• I will abide by the code of conduct

[johnzhou721]

Why can’t you push to main? Some bizarre git issue? Just curious and thanks for helping me clean this up

[freakboy3742]

Why can’t you push to main? Some bizarre git issue? Just curious and thanks for helping me clean this up

Because it's your main.

A PR, by definition, is a set of proposed changes; If you've opened a PR on my repo, then it's reasonable to assume that it's OK for me to make modifications.

However, your main branch could be a branch that you're using for a specific purpose. As a result, Github doesn't give me permission to push to your main branch by default. It is possible to configure your repo to give me access... but for the sake of one PR, it's easier to just use a separate PR.

More generally - submitting pull requests from the main branch is a bad idea, because you then don't have a "clean state of the upstream" readily available. For example, when this PR is merged, you won't be able to update your main to get a clean state from which to branch off - you'll need to do some rebasing or resetting to get back to a clean state.

I have asked Github many times to provide an option to disable PRs from main because of the complications it causes for contributors, but they have consistently ignored the request.

[johnzhou721]

Sorry. First time using GitHub fork system with git so sort of confused and thanks for the clarification!!

[johnzhou721]

CIs are passing. Merge?