[FEATURE] Support self-signed certificates in builds

[diksha1999]

Is there an existing feature request for this?

• I have searched the existing feature requests

Is your feature request related to a problem or use-case? Please describe.

Shipwright builds are failing due to the issues while executing the first "source-default" step of ShipWright when a self-signed custom CA bundle is being used for a Git server.
Scenarios:

1. Cloning source code from a private git server
2. Pulling container images from a private container registry
3. Pulling dependencies from a private repository (ex: Artifactory).

Describe the solution that you would like.

Support for self-signed enterprise certificates in shipwright builds.

In enterprise environments, TLS certificates are often issued by a "corporate" certificate authority that is not globally trusted by RHEL. Actions that use HTTPS as transport (ex: cloning git source, pulling container images, downloading dependencies) need to be able to find and utilize the correct certificate authority.

Describe alternatives you have considered.

No response

Anything else?

Related Openshift Builds epic link:
https://issues.redhat.com/browse/BUILD-1152

[diksha1999]

Related Openshift Builds epic link:
https://issues.redhat.com/browse/BUILD-1152

[SaschaSchwarze0]

Sounds like an optional secret reference in the Git Source where there referenced secret contains a ca.crt. Is that what you are looking for @diksha1999 ?