One solution would be to load those links from environment variables, similar to how it's done with API access keys and other sensitive data. This would mildly inconvenience the devs by having to copy the links to those types of content by hand and set the vars before running the tests, but none of the "infringing" links would be present in the repo itself.