add script to parse broken links

[BRKalow]

🔗 Relevant links

• Preview link 🔎
• Asana task 🎟️

🗒️ What

$ muffet --rate-limit=16 https://developer.hashicorp.com --json | tee broken_links.json
$ npx hc-tools ./scripts/parse-broken-links.ts > out.txt

🤷 Why

🛠️ How

📸 Design Screenshots

🧪 Testing

💭 Anything else?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
dev-portal	✅ Ready (Inspect)	Visit Preview	Sep 21, 2022 at 6:59PM (UTC)

[github-actions]

Some suggested prefixes and emojis that may help to write clear, actionable code review comments:

Praise 🙌	Question 🙋	Thought 💭	Blocker 🚧	Future 📌	Optional 🎨	Nitpick ⛏️

Expand for comment prefix descriptions

Prefix+Emoji	Description
Praise 🙌	Use to highlight something positive. It's nice to try to leave one per review, but don't leave false praise just to leave one of these comments.
Question 🙋	Use to gain clarity from the code author. The conversation could evolve into any one of these other categories. Only the reviewer should resolve these comment threads.
Thought 💭	Use to share context, leave a breadcrumb, or share an idea that came up while reviewing.
Blocker 🚧	Use to request changes that block merging the current PR. Only the reviewer should resolve these comment threads.
Future 📌	Use to request changes that the code author can choose to address in the current PR or a follow-up one.
Optional 🎨	Use to suggest optional changes that you feel strongly about but ultimately defer to the code author to make a decision on. These can be comments that turn into valuable conversation starters for adopting new code styles, guidelines, or team practices.
Nitpick ⛏️	Use to suggest changes based on loose opinions or personal preferences. The difference between this and Optional 🎨  is how strong the code reviewer's opinion is.

[github-actions]

📦 Next.js Bundle Analysis

This analysis was generated by the next.js bundle analysis action 🤖

This PR introduced no changes to the javascript bundle 🙌

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

Bryce Kalow seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}