Improve PhishingController error handling

The PhishingController error handling for config updates has room for improvement. Currently config update failures are swallowed, so there is no opportunity for caller to discover this or retry. Some types of failure are not even logged.

We should ensure that config update failures are not suppressed with `updatePhishingLists` is called, so that the caller is aware when a failure has occurred. In any circumstance where it is necessary to suppress config update failures (e.g. in `test`), we should at least ensure the failure is logged, for debugging purposes.

Start at the PhishingController entry point and trace where updatePhishingLists is called, including the test path mentioned in the issue. Determine which config-update failures are currently suppressed, then ensure callers can discover or retry failures and that any intentionally suppressed failures are logged.

Written by the indexing model from the issue text.