Fix FragmentTransaction replace() behavior

This is from AOSP Gerrit Review, was just Pushed, so not yet merged.
It is a definate problem though:
case OP_REPLACE should not remove only every other fragment.
It needs to be fixed. So here it is.
-----------------------------------

According to FragmentTransaction's reference, replace()
should be equivalent to remove()'ing every fragment in
a given container and then adding the specified fragment
to replace those that were removed.

Commit ee76efb74b5886f98cdfebfbefe9b69224e016fb broke
this intended behavior in the framework.

This patch makes it so that the removal loop doesn't
end prematurely. It also fixes an issue where the
replace operation would remove fragments regardless
of their container after encountering the first fragment
with a matching container ID.

Relevant issues:
http://b.android.com/43265
http://b.android.com/52112
http://b.android.com/53393
http://b.android.com/68856
http://b.android.com/70803

Change-Id: Ica4691746ab8979ed974a998e85324e4feacc5e3
Signed-off-by: Eddie Ringle <eddie.ringle@gmail.com>
PSB: duplicate includes can DIAF

Change-Id: I2c3b683856c39aab041a324db8252a7bc7d013fa