feat(images): fetch TLS certificate from secret for upload endpoints

[hardcoretime]

Description

Added TLS certificate retrieval from secrets for upload endpoints to fix TLS verification errors when using self-signed certificates.

Why do we need it, and what problem does it solve?

When the cluster uses a self-signed certificate for the ingress controller, the IsUploaderReady function fails with TLS verification error because it doesn't have access to the TLS secret containing the CA certificate. This prevents users from uploading images through the upload endpoint.

The fix retrieves the TLS secret from the cluster and passes it to the IsUploaderReady function, enabling proper TLS verification.

What is the expected result?

Upload endpoints work correctly with TLS verification, even when the ingress controller uses self-signed certificates. The implementation also supports legacy naming of TLS secrets for backward compatibility.

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: api
type: feature
summary: "Fetch TLS certificate from secret for upload endpoints to enable TLS verification with self-signed certificates"

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.