FIX: Make visionOS a supported build target from 2022.3 (ISXB-1539)

[jfreire-unity]

Description

Fix error reported in https://jira.unity3d.com/browse/ISXB-1539

Testing status & QA

I created a new 2022.3 LTS project (currently at .61f) and saw that the reported error had disappeared.

Overall Product Risks

• Complexity: 0
• Halo Effect: 0

Comments to reviewers

Please describe any additional information such as what to focus on, or historical info for the reviewers.

Checklist

Before review:

• Changelog entry added.
  • Explains the change in Changed, Fixed, Added sections.
  • For API change contains an example snippet and/or migration example.
  • JIRA ticket linked, example (case %%). If it is a private issue, just add the case ID without a link.
  • Jira port for the next release set as "Resolved".
• Tests added/changed, if applicable.
  • Functional tests Area_CanDoX, Area_CanDoX_EvenIfYIsTheCase, Area_WhenIDoX_AndYHappens_ThisIsTheResult.
  • Performance tests.
  • Integration tests.
• Docs for new/changed API's.
  • Xmldoc cross references are set correctly.
  • Added explanation how the API works.
  • Usage code examples added.
  • The manual is updated, if needed.

During merge:

• Commit message for squash-merge is prefixed with one of the list:
  • NEW: ___.
  • FIX: ___.
  • DOCS: ___.
  • CHANGE: ___.
  • RELEASE: 1.1.0-preview.3.

After merge:

• Create forward/backward port if needed. If you are blocked from creating a forward port now please add a task to ISX-1444.

[Pauliusd01]

Checked whether the error is gone when switching to the visionOS player (In Editor only, I only used the player extensions, don't have the device itself to check anything in game)

[mtschoen-unity]

In Editor only, I only used the player extensions, don't have the device itself to check anything in game

Input was still working for me on device when I encountered this earlier today. I think the editor log is the only real issue.