delete recovery policy on changing build types
delete recovery policy on changing build types

When the build type changes (for example, from "shamu-userdebug"
to "shamu-user"), the build system doesn't delete all files
and start over. Rather, build artifacts from the old build type
are reused for the new build type.

This is problematic for the recovery SELinux policy, which differs
between build types. Reusing a userdebug policy on a user build
is inappropriate and could lead to security bugs.

Force the deletion of the recovery SELinux policy when changing
build types, so it can be properly regenerated. This is consistent
with how we treat the normal SELinux policy (see commit
a8b3d54101eccb9950651103c199edf0ce2520f7).

(cherry picked from commit 3cb10bbd3b376aecbbefffbe4d43105665bad345)

Change-Id: I1d8ad7e06112777c66abed4546dadb85d35e33e1

xorware/android_build,xorware/android_build,xorware/android_build,xorware/android_build,xorware/android_build