ci(contents): ping affected mirror sites

[ZenithalHourlyRate]

When there is a PR changing the content of one mdx, affected mirror site admins should be notified, and we should set up approving mechanisms (e.g. at least 2 approvals) (thanks to @RalXYZ)

We should maintain two map

• contents -> affected mirror sites (from mirrorz.json)
• mirror site -> mirror admin github account (TODO)
  • There should be doc admins and other admins

     "TUNA": {
         "help": @somebody,
         "chores": @another,
      }
  

The first part is a CI commenting in the PR that what mirror sites are affected.

After we set up the admin map, the CI should mention them.

[ZenithalHourlyRate]

There should be a third metadata about what helps a mirror site is using. E.g. SDU uses ubuntu and rocky from mirrorz-help but uses its own debian and archlinux help

SDU: ["ubuntu", "rocky"]

If a site has such metadata, then even if it is mentioned in mirrorz.json, it wont be pinged

More generally, there should be an opt-in and opt-out mechanism for each mirror item.

• rsync mirror should be opt-out (in case they excluded some path)
• script mirror should be opt-in (if it is verified then display)