Fix input method switch handling in autofill

* this reverts ag/11592765 since it causes a regression for b/145949573
  in the following case:
  1. user taps on a field for which autofill returns null and augmented
     autofill is triggered
  2. user goes home, which sets the mExpiredResponse to true
  3. user comes back to the app, now tapping on the input field over
     and over, each tap will trigger a new augmented autofill request
* the fix is to revert the above patch, and then handle the input
  method switch for augmented autofill case by setting the current
  view to null, and also setting the augmented autofill id to null,
  such that the entire autofill flow will be executed again.
* note that this patch changes one behavior - in case regular autofill
  returns null and augmented autofill is triggered, switching input
  method and tap on the field again, it will trigger regular autofill
  again (before this patch, it will only trigger augmented autofill)

Test: relevant cts tests
Test: manual testing that on the chat app, switching input method
      and then tap on the field again triggers a new request
Bug: 150483555
Bug: 157412832

Change-Id: I0868ff62047f66402885f9821f7981ca4596f76b