PRs updates may cause unwanted PR creation in `docker-library/official-images`

Situation

When Dockerfile-template.* changes are made and Dockerfile updates in the release line directories are also made, then the repo automatically triggers a PR to build a new release. The workflow official-pr is responsible for this.

Unless the update is part of a new release, then Dockerfile updates should generally not be done manually. These updates should be left to the automated processes that are triggered when the repo's automatic-updates.yml polling workflow detects a new Node.js release.

Suggestion

Research the background and add instructions to the CONTRIBUTING document about when Dockerfile updates should be made directly, and when it should be left to automation.

For those cases where no direct Dockerfile update should be included in a PR, describe also how to test such PRs.

阅读 CONTRIBUTING.md 以及 .github/workflows/official-pr.yml 和 automatic-updates.yml，以了解 Dockerfile 更改何时会触发官方镜像 pull request。更新 CONTRIBUTING.md，加入直接更新的例外情况，以及测试不应包含 Dockerfile 更新的 PR 的说明；完成标准是清楚记录这两种情况。