Add timeout configuration for ocm v2

[piotrjanik]

Description

Depending on their location, users might need to modify the timeout settings in the HTTP client used by oras to improve handling of network issues they encounter.

Currently, we're using Oras retry.DefaultClient, which sets default values.
With this task, we want to let users decide which values to use.

A similar task has already been completed for the legacy OCM, and this task is for the new OCM. We want to ensure that both can use the same HTTP configuration.

type: http.config.ocm.software/v1alpha1
# --- Timeouts ---
timeout: "0s"
tcpDialTimeout: "30s"
tcpKeepAlive: "30s"
tlsHandshakeTimeout: "10s"
responseHeaderTimeout: "10s"
idleConnTimeout: "90s"

Done Criteria

• http.config.ocm.software/v1alpha1 config created
• backward comaptibility with legacy ocm
• Code has been reviewed by other team members
• Analysis of existing tests (Unit and Integration)
• Unit Tests created for new code or existing Unit Tests updated
• Integration Test Suite updated (includes deletion of existing unnecessary Integration Test and/or creation of new ones if required)
• Enduser Documentation updated (if applicable)
• Internal technical Documentation created/updated (if applicable)
• Successful demonstration in Review