automate broken link reporting in markdown files

Broken or bad links in markdown files could be identified and reported using automation to improve the usability of the documentation.

Expected Behavior or Use Case

Broken links in markdown files are identified and reported in an automated way.

Presto Component, Service, or Connector

Documentation, and the wiki - markdown files in the Presto repo.

Possible Implementation

Perhaps the GitHub Action Baler – BAd Link reportER would be a good way to automate this process. This is merely a suggestion, I'm very open to other proposed solutions.

Example Screenshots (if appropriate):

Context

When I found the broken link in CONTRIBUTING.md and Presto Development Guidelines - see PR 21808 - I considered that finding broken links in the Presto repos could be automated. A quick search later and I'd found the GitHub Action Baler – BAd Link reportER.