letsencrypt
CA and cert-checker need to know whether to allow Test CT logs
The RA configures its log list based on a boolean indicating whether it should submit to test logs. We set that boolean to True in Staging, giving that environment access to CT logs that aren't actually Usable in browsers.
However, the CA and the cert-checker both also use the log list in order to power our e_scts_from_same_operator custom lint. But when those components build their loglist for that lint, they unconditionally say no test logs.
Historically we haven't run into this bug because we've been using different log lists in prod and staging, neither of which marked any logs as "Test" logs. Now we're switching to use a single log list in both environments, distinguishing which logs can be used by the log list's built-in "Test" indicator. When we tried to do so, Staging's lints immediately started failing, because none of the test logs used there were included in the lint's log list, and therefore the lint believed that no RFC6962-compliant logs has provided SCTs for the cert.
We can temporarily disable this lint in Staging, but that's not a good long term fix. We need a way for the CA and cert-checker to correctly initialize their lint loglist with or without Test logs, as appropriate.
