chore(ci): add guardrail to prevent outdated version references in CONTRIBUTING.md

[Nsanjayboruds]

Current Behavior

Contributor docs can become stale when dependency versions change in package.json.
For example, setup/troubleshooting sections may continue to reference old React/Gatsby versions, which causes confusion for newcomers and extra maintainer support.

Desired Situation

Add an automated guardrail that validates key version references in contributor-facing docs (starting with CONTRIBUTING.md) against current values in package.json.

Expected outcome:

• CI fails when documented versions are outdated.
• CI passes when docs and dependencies are aligned.
• Failure message clearly indicates what file/value should be updated.

---

Contributor Resources and Handbook

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.

• 📚 See contributing instructions.
• 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack.

Join the Layer5 Community by submitting your community member form.

[Nsanjayboruds]

Hi @leecalcote

I’m a newcomer to the Layer5 community and I’ve already submitted the community member form. I would love to contribute to this issue.

Could you please assign it to me? I’d be happy to work on it. Thank you!