[FR] Enforce direct-link rule: fail CI on HTTP 3xx redirects in README

## Use case
`CONTRIBUTING.md` line 12 forbids shortened/proxy/redirect links, but `npx markdown-link-check@3.14.2` (`.github/workflows/lint.yml`) only flags 4xx/5xx, so 301 redirects pass silently. Example live today: `README.md` line 28 `segmentio/nightmare` -> 301 `segment-boneyard/nightmare`; line 34 `GoogleChrome/puppeteer` -> 301 `puppeteer/puppeteer`.

## Proposal
Add a CI step that fails on 3xx. Options: (a) parse `markdown-link-check` verbose output for `->` redirect lines; (b) add `lychee --no-progress --require-https --exclude-mail --max-redirect 0 README.md`; (c) a small shell loop calling `curl -sIo /dev/null -w '%{http_code}' ` per link.

## Existing art
`lychee-action` (used by many awesome-lists) supports `--max-redirect 0`.

## Not-a-bug caveat
Current workflow is functional once the branch-name bug (separate issue) is fixed; this FR strengthens it.

Thanks for maintaining angrykoala/awesome-browser-automation!

Start with .github/workflows/lint.yml and CONTRIBUTING.md line 12, then inspect the current markdown-link-check step against the redirects listed in README.md lines 28 and 34. Compare the proposed redirect-handling options and verify the workflow fails for HTTP 3xx links while retaining its existing link checks; the separate branch-name issue is out of scope.

索引モデルが issue の本文から書いたものです。