FIX: Fix for event processing when operating in Manual Update mode (case ISXB-1141)

[AlexTyrer]

Description

A recent change was made to correct event processing when the Input System Update Mode was set to Fixed Update mode (#2026).

This has caused an issue when processing in Manual Mode resulting in "ISubmitHandler.OnSubmit is not being called when Update Mode is set to "Process Events Manually""

This change addresses that problem.

Testing status & QA

Local testing with user supplied project and scripts - tested all three modes (Fixed, Dynamic, Manual)
Automated testing.

Overall Product Risks

• Complexity: Low
• Halo Effect: Low

Comments to reviewers

None in particular.

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.

[ekcoh]

LGTM, good catch. My biggest takeaway with all this is that polling APIs for events gets unnecessarily complex when multiple timelines are introduced. I have said it before, a reality for each timeline basically needs to exist.