FIX: InputTestFixture stepping updates in [UnityTest]s incorrectly (case 1341740).

[Rene-Damm]

Fixes 1341740 (FogBugz).

Description

Do this in a [UnityTest] would fail

Press(Gamepad.current.buttonSouth);
yield return null;
Assert.That(Gamepad.current.buttonSouth.wasPressedThisFrame, Is.True);

The reason is that calling Press with the default queueEventOnly=false argument would imply running an InputSystem.Update right away. Thus an extra frame would be inserted.

Changes made

queueEventOnly is now always considered true in a [UnityTest].

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.
  • FogBugz ticket attached, example ([case %number%](https://issuetracker.unity3d.com/issues/...)).
  • FogBugz is marked as "Resolved" with next release version correctly set.
• 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.

[ekcoh]

Seems like change causes multiple test failures, incorrect fix or test cases needs update due to new corrected behavior?