Add requireAllDemandsAndIgnoreOthers flag

[Nohac]

This PR adds an extra option requireAllDemandsAndIgnoreOthers (name tbd) to the azure pipeline scaler which ensures that all demands in the scaler definition is present in the incoming job, while ignoring any other demands the job may have.

This is different from requireAllDemands which requires all demands to be an exact match.

Checklist

• When introducing a new scaler, I agree with the scaling governance policy
• I have verified that my change is according to the deprecations & breaking changes policy
• Tests have been added
• Changelog has been updated and is aligned with our changelog requirements
• A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
• A PR is opened to update the documentation on (repo) (if applicable)
• Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #5579

[semgrep-app]

Semgrep found 1 context-todo finding:

• pkg/scalers/azure_pipelines_scaler_test.go
  • L363 - Triage

Consider to use well-defined context

_{Ignore this finding from context-todo.}

Semgrep found 1 no-direct-write-to-responsewriter finding:

• pkg/scalers/azure_pipelines_scaler_test.go
  • L351 - Triage

Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'.

_{Ignore this finding from no-direct-write-to-responsewriter.}

[semgrep-app]

Semgrep found 1 context-todo finding:

• pkg/scalers/azure_pipelines_scaler_test.go
  • L363 - Triage

Consider to use well-defined context

_{Ignore this finding from context-todo.}

Semgrep found 1 no-direct-write-to-responsewriter finding:

• pkg/scalers/azure_pipelines_scaler_test.go
  • L351 - Triage

Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'.

_{Ignore this finding from no-direct-write-to-responsewriter.}

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed due to inactivity.

[JorTurFer]

Could you fix the DCO check and update the changelog too?

[JorTurFer]

/run-e2e pipeline
Update: You can check the progress here

[semgrep-app]

Semgrep found 1 context-todo finding:

• pkg/scalers/azure_pipelines_scaler_test.go
  • L363 - Triage

Consider to use well-defined context

_{Ignore this finding from context-todo.}

Semgrep found 1 no-direct-write-to-responsewriter finding:

• pkg/scalers/azure_pipelines_scaler_test.go
  • L351 - Triage

Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'.

_{Ignore this finding from no-direct-write-to-responsewriter.}