Pr trggiers generated by code (#17247)
### Description
1. Refactor the trigger rules generation.
2. Skip all doc changes in PR pipelines.
### Motivation and Context
Make all trigger rules generated by running set-trigger-rules.py to
reduce inconsistences.
It's easily to make mistakes to copy&paste manually.
For example: these 2 excludes are different, Why?
https://github.com/microsoft/onnxruntime/blob/4e6cec4d09ca399c66541ee61109c3099af1a463/tools/ci_build/github/azure-pipelines/linux-ci-pipeline.yml#L16-L18
https://github.com/microsoft/onnxruntime/blob/4e6cec4d09ca399c66541ee61109c3099af1a463/tools/ci_build/github/azure-pipelines/linux-gpu-ci-pipeline.yml#L27-L29
### Note
All changes in workflow yamls are generated by code.
Please review the **skip-js.yml, skip-docs.yml and
set-trigger-rules.py**.
@fs-eire, please double check the
filter rules in skip-js.yml
and the skipped workflows
https://github.com/microsoft/onnxruntime/blob/7023c2edff7704622ab65ce610f7de51a2ccbfae/tools/ci_build/set-trigger-rules.py#L14-L41
