ICU-22532 Trigger CI workflows when workflow definitions change

[echeran]

In addition to running C++ tests when C++ code changes, we should also run C++ tests when the configs for the tests change, too.

Also, as a side task, I'm removing the batch: true from the Azure pipelines in the triggers for when merging to main so that Github will show the Azure CI checks alongside the Github Actions CI checks for each merge commit on main.

Checklist

• Required: Issue filed: https://unicode-org.atlassian.net/browse/ICU-22532
• Required: The PR title must be prefixed with a JIRA Issue number.
• Required: The PR description must include the link to the Jira Issue, for example by completing the URL in the first checklist item
• Required: Each commit message must be prefixed with a JIRA Issue number.
• Issue accepted (done by Technical Committee after discussion)
• Tests included, if applicable
• API docs and/or User Guide docs changed or added, if applicable

[jira-pull-request-webhook]

Notice: the branch changed across the force-push!

• .github/workflows/icu_docs.yml is different
• .github/workflows/icu_valgrind.yml is different
• .github/workflows/icu4c.yml is different
• .github/workflows/icu4j.yml is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

[echeran]

@rp9-next I think the Azure pipeline CI-ICU4J should have been triggered here, just like we have for CI-ICU4C, but it was not. The pipeline yaml file for ICU4J is similar to ICU4C. Do you know what the reason is? Is there something that can be adjusted in the Azure Devops Pipelines dashboard to make it run?

[rp9-next]

@rp9-next I think the Azure pipeline CI-ICU4J should have been triggered here, just like we have for CI-ICU4C, but it was not. The pipeline yaml file for ICU4J is similar to ICU4C. Do you know what the reason is? Is there something that can be adjusted in the Azure Devops Pipelines dashboard to make it run?

@echeran The ICU4J is getting triggered but it does not come up in the GitHub PRs..
https://dev.azure.com/ms/icu/_build/results?buildId=547546&view=results

I think you were mentioning something about adding it to the GitHub settings but couldn't find it..
Could you check if the CI-ICU4J is visible now?