AIP-9672: Add resourceRetryStrategy for quota-aware retries

[abdulazillow]

Description

Adds ResourceRetryStrategy field to Trigger struct enabling different retry behaviors for ResourceQuota errors vs regular validation errors. When resourceRetryStrategy is configured, quota-related errors (e.g., "exceeded quota") use the specified retry strategy while other errors use the default retryStrategy.

Configuration

Sensors can now configure separate retry strategies for resource constraint errors:

triggers:
- template:
    name: my-trigger
  retryStrategy:
    steps: 2
    duration: 5s
    factor: 2.0
  resourceRetryStrategy:  # NEW FIELD
    steps: 4
    duration: 10s
    factor: 1.5

Backward Compatibility

Maintains full backward compatibility - existing sensors continue working unchanged, while new sensors can opt into quota-aware retries. When resourceRetryStrategy is not specified, all errors use the default retryStrategy.

Test Results

Successfully tested in sandbox environment with actual ResourceQuota limits:

  | Test | Error Type                                  | Strategy Used         | Retries | Total  Time | Status   |
  |------|---------------------------------------------|-----------------------|---------|------  ------|----------|
  | #1   | Quota exceeded                              | resourceRetryStrategy | 4       | ~55s        | ✅ PASSED |
  | #2   | Validation error                            | retryStrategy         | 2       | ~6s        | ✅ PASSED |
  | #3A  | Validation error (no resourceRetryStrategy) | retryStrategy         | 2       | ~5.5s        | ✅ PASSED |
  | #3B  | Quota error (no resourceRetryStrategy)      | retryStrategy         | 2       | ~15s        | ✅ PASSED |

All tests validate correct retry strategy selection and maintain backward compatibility.

[dhanashritidke11]

Looks good to me. Thanks for sharing the test results.