Refactor CA certificate handling
Currently, custom CA certificates not trusted by default are stored within the account, but they need to be added to the global state to make requests in various network jobs work.
Instead of using the global state, we should rework our network access manager(s) to store custom the CA certificates and inject them on new requests (e.g., in createRequest).
Since we plan to introduce a custom network access manager for the core jobs as well, this is the perfect opportunity to reduce the amount of duplicate code and move common behavior into a common (abstract) base class.
This issue was marked stale because it has been open for 30 days with no activity. Remove the stale label or comment or this will be closed in 7 days.