input: fix possible miss of 'next-frame' requests

So, finally, next-frame is harder than prev-frame.

The current 'next-frame' workaround works by luck (hope it's enough for 3.0).

This MR introduce a new workaround and a proper next-frame unit test.

See all commits.

Really fixes #28145 (closed)

Fixes #29487