Why:

Some users would like to use the Secure features (e.g. SAST) on a
network that has a custom CA. These networks replace the public
certificate with a private one from a custom CA so that they can monitor
HTTPS traffic.

This change addresses the need by:

* Add a initialize package with the responsibility of initializing an
  analyzers environment.
* Add intialize hook to all commands.

Side effects:

* There is a chance that there is a naming collision with the default
  ca cert bundle path. If a collision occurs, then the path will either
  be overwritten or end in an error if write permission is not given to
  the current user. All that being said, it does seem unlikely for the
  path to collide as it is namespaced to gitlab.