CHANGE: Added message to notify the user if a PlayerInputComponent fails to bind a control scheme (ISXB-1020)

[lyndon-unity]

Description

Added message to notify the user if a PlayerInputComponent fails to bind a control scheme (ISXB-1020)
This can happen if there are multiple game objects with PlayerInputComponent's and not enough devices to support them

Changes made

Added an error message in the case when the list of available control schemes has been exhausted

Testing

Ran on the test case in the bug report and it fires a message on PC when only a keyboard/mouse plugged in.
(Does not fire of a touchscreen is also connected)

Ran all the unit tests and they all pass

Risk

Potentially there is a use case I missed which doesn't warrant the error message

Checklist

Before review:

• Changelog entry added.
• Ran existing tests
• No new docs

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]

I'm still reproducing it with no error showing up, do I need to do anything extra or is this a proper issue?

1726740435.inputTest_-_GameplayScene_-_Windows._Mac._Linux_-_.mp4

[lyndon-unity]

I'm still reproducing it with no error showing up, do I need to do anything extra or is this a proper issue?

1726740435.inputTest_-GameplayScene-_Windows.Mac.Linux-.mp4

That's the expected result when touchscreen and keyboard present, the error only shows when just keyboard present (i.e. only one valid control scheme that can be bound)

[Pauliusd01]

Can you change it so it says "(all control schemes are already paired to matching devices)" or "(all control schemes are already paired to available devices)" to make it a bit more clear on what the issue is? Since I saw plenty of schemes to go around and it wasn't immediately obvious to me why I'd get this error as a user

[lyndon-unity]

Can you change it so it says "(all control schemes are already paired to matching devices)" or "(all control schemes are already paired to available devices)" to make it a bit more clear on what the issue is? Since I saw plenty of schemes to go around and it wasn't immediately obvious to me why I'd get this error as a user

Done.
I've also switched from error to warning to match feedback from Hakan on a port of this change.