[ADI][45/N] bypass developer verification in emergency cases

An emergency situation is when the developer verification policy
is BLOCK_FAIL_CLOSED, and the verifier fails to be launched or
connected or it times out, while one of the following apps are being
installed or updated:

* The verifier itself
* The original update-owner of the verifier as specified in sysconfig
* The emergency installer of the verifier's original update-owner

Because these are critical packages, we don't want to block them in the
emergency situations. This CL allows the developer verification bypass
under such situations.

BUG: 360129657
FLAG: android.content.pm.verification_service
Test: atest CtsRootDeveloperVerificationPrivInstallerTarget36TestCases CtsRootDeveloperVerificationInstallerTarget36TestCases CtsRootDeveloperVerificationPrivInstallerTarget35TestCases CtsRootDeveloperVerificationInstallerTarget35TestCases
Test: atest com.android.server.pm.PackageInstallerSessionTest

Change-Id: I925b2b4cfb7c92277adef9f09bf322fb5af9d3eb