Add production Cast CRL certificate.

components/cast_certificate/cast_crl_unittest.cc

Index: components/cast_certificate/cast_crl_unittest.cc
diff --git a/components/cast_certificate/cast_crl_unittest.cc b/components/cast_certificate/cast_crl_unittest.cc
index d65b3a63b1e8d1f0ffaefd93cbebbb65e49a2623..765b00cb45edbd5995f6e3d40fac1bc29b22aec5 100644
--- a/components/cast_certificate/cast_crl_unittest.cc
+++ b/components/cast_certificate/cast_crl_unittest.cc
@@ -90,6 +90,8 @@ bool TestVerifyRevocation(TestStepResult expected_result,
 
 // Runs a single test case.
 bool RunTest(const DeviceCertTest& test_case) {
+  ResetCRLTrustAnchorForTest();

[eroman, 2016/08/03 22:47:58]

This seems problematic, in that running the tests can pollute global state for
subsequent tests.
The trust anchor is not necessarily reset here upon completion of the test (just
upon entry).

Can this be solved by one of these solutions, in order of preference.

  (a) Make the trust store an explicit dependency -- this could be done by
introducing a *ForTest() flavor of the verification function that takes a
TrustStore dependency. The advantage of this approach is tests to not mutate a
singleton, and mutation of the singleton no longer needs to be exposed. I think
this is my preferred approach.

 (b) Keep the current organization but instead of exposing a "Set/Reset*" method
for test, use a scoped setter. This ensures that override of the trust anchor is
short-lived to particular test cases or test fixtures.

 (c) Call reset in the tear down method for test fixture, so after running the
test global state is reset.

[ryanchung, 2016/08/04 18:46:43]

Done. Went with solution a).
Thanks!

+  ResetTrustAnchorForTest();
   bool use_test_trust_anchors = test_case.use_test_trust_anchors();
   if (use_test_trust_anchors) {
     const auto crl_test_root =