I was thinking about this check more and I think this might actually become a source of flakes on CI. Also since this check would be invoked for each change and some URLs might become unreachable over time, we may end up with failing CI for main branches that would not be directly related to the changed code.

I think the check is still useful, but I'd propose making it a warning instead and log the findings to the output (avoid throwing an error). In this case we would have all the necessary info and tooling to do these cleanup once in a while, but avoid flakes and CI failures due to 3rd party websites availability.