Change behavior around removing mLooperProcessed

When removing a message that is also mLooperProcessed, we should set
mLooperProcessed to mLooperProcessed.next instead of running through the
stack for a non-removed message. This is because we may accidentally add
these skipped removed messages to the heap if the thread that marked
them for removal hasn't pushed them onto the freelist yet.

Test: presubmit (FrameworksCoreTests_messagequeue)
Bug: 444085764
Flag: build.RELEASE_PACKAGE_MESSAGEQUEUE_IMPLEMENTATION
Change-Id: I83536c0ef383f4984a3be84ce9c9a129ea39b275