[New Feature]: Validation pipeline give Validation-Domain when the installer comes from a different domain

[DuckDuckStudio]

Description of the new feature/enhancement

The validation pipeline (maybe)should give Validation-Domain when the installer comes from a different domain than the installer url of the previous version (for github.com or similar repository urls(like gitee.com), it should be validated to come from the same repository).

This is done to ensure that the source of the package is consistent. If the publisher does change their distribution server, we can waivers this error in that PR, and since subsequent PRs are manifest against the previous version, subsequent PRs will not have this error again.

原文

验证管道应该在安装程序来源与之前的清单中的来源不同时添加 Validation-Domain 标签（对于 github.com 和 gitee.com 等存储库链接，应当验证它们是否来自同一存储库）

这是为了确保软件包清单中的安装程序都来自相同的源（而不是一会sourceforge一会github这样）。如果软件包发布者更换了他们的服务器，则可以在出现此错误的一个 PR 中豁免此错误。由于验证管道是向最新(New version PR版本的上一个版本)版本比较，所以后续 PR 不会再出现此错误。

Proposed technical implementation details (optional)

Add a check to the existing step of validating the domain to check that the source of the installer in the PR is the same as the previous manifest. If different, add a Validation-Domain label to the PR.

原文

在现有的 验证域 检查步骤中添加一个检查来确认该 PR 中的安装程序来源与上一个版本的清单中的安装程序来源是否一致。如果不同，则向 PR 添加 Validation-Domain 标签

[stephengillie]

I'm not sure of the source that tells the pipeline to add this and other labels, but my guess is that a simple text match against a list of terms might be all that's used. I've added an "autowaiver" system to my approval automation, which checks the InstallerUrl from the files in the PR's commits, against a CSV list. For Validation-Domain , if the domain matches, then the label is removed and Validation-Completed Validation passed is added. This currently runs at :20 and :50 after every hour, when my laptop is open.