The policy code used to block the profile-ready state, waiting for a policy fetch to happen, even in the case where the profile was synchronously initialized after a browser crash. This behavior is incorrect, but some tests rely on being able to inject policy into a synchronously-initialized profile.

The new implementation of the policy stack forbids this case, and properly load-and-initialize synchronous profiles synchronously. To accommodate tests that rely on the old behavior, we've added the kWaitForInitialPolicyFetchForTest flag. We should rewrite these tests (arc_cert_store_bridge_browsertest.cc and platform_keys_apitest_nss.cc) to run in an asynchronously-initialized user profile instead of in a synchronously-initialized login profile.

Assigning to emaxx/edman as the owners of the two misbehaving tests.