feat(run-pod): allow image pull retries in run pod collector

[diamonwiggins]

Description, Motivation and Context

This PR adds a new allowImagePullRetries field to the RunPod collector configuration to control how ImagePullBackOff errors are handled.

Problem: Currently, when a RunPod collector encounters a pod in ImagePullBackOff state, it immediately fails regardless of any configured timeout. This prevents users from handling scenarios where image pulls might eventually succeed (e.g., temporary registry issues, authentication delays, or slow networks).

Solution: Added an optional allowImagePullRetries boolean field that allows ImagePullBackOff conditions to respect the configured timeout instead of failing immediately.

Behavior:

• When allowImagePullRetries: false (default): Maintains existing behavior - fails immediately on ImagePullBackOff
• When allowImagePullRetries: true: Waits for the configured timeout, allowing image pull retries to potentially succeed

Usage Example:

- runPod:
    timeout: "5m"
    allowImagePullRetries: true
    podSpec:
      containers:
      - name: my-container
        image: my-private-image

Checklist

• New and existing tests pass locally with introduced changes.
• [] Tests for the changes have been added (for bug fixes / features)
• The commit message(s) are informative and highlight any breaking changes
• Any documentation required has been added/updated. For changes to https://troubleshoot.sh/ create a PR here

Does this PR introduce a breaking change?

• Yes
• No