Fix regression in adding recents input consumer leading to ANR

- Because cantReceiveTouchInput() accounts for whether an activity is
  being controlled by recents (it shouldn't receive touches), we happen
  to skip adding the recents input consumer below.  However, because the
  activity input window is skipped and the input consumer is not added,
  we end up with no focused window, which then means that the next touch
  on a nav button will try to inject a keyevent to no focused windows,
  which triggers an ANR.

  Ensure that we fall through to the logic below to add the recents
  input consumer specifically in the case where an app window shouldn't
  receive touches, but should have the recents input consumer applied.

Bug: 156394972
Test: Take surface trace while swiping up and ensure the input consumer
      is relz to the app window being controlled

Change-Id: I9606dbef4565508514f4ff2f9ef464e9737bd7cc
Signed-off-by: Winson Chung <winsonc@google.com>