Add support for custom CA certs

What does this MR do?

Add support for custom CA certs

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.

What are the relevant issue numbers?

• SAST: gitlab-org/gitlab#11797 (closed)
• Dependency Scanning: gitlab-org/gitlab#208721 (closed)
• Container Scanning: gitlab-org/gitlab#208720 (closed)

Does this MR meet the acceptance criteria?

• Changelog entry added
• [-] Documentation created/updated for GitLab EE, if necessary
• [-] Documentation created/updated for this project, if necessary
• [-] Documentation reviewed by technical writer or follow-up review issue created
• Tests added for this feature/bug
• [-] Job definition updated, if necessary
• Conforms to the code review guidelines
• Conforms to the Go guidelines
• Security reports checked/validated by reviewer