fix: remove unused ref to internal catalog

[mjang]

Proposed changes

Problem: Current archetypes include unneeded info. Problem ID'd in this comment.

Solution: Remove unneded info

Testing: n/a

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

• I have read the contributing guidelines
• I have signed the F5 Contributor License Agreement (CLA)
• I have rebased my branch onto main
• I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
• I have ensured that the commit messages adhere to Conventional Commits
• I have ensured that documentation content adheres to the style guide
• If the change involves potentially sensitive changes¹, I have assessed the possible impact
• If applicable, I have added tests that prove my fix is effective or that my feature works
• I have ensured that existing tests pass after adding my changes
• If applicable, I have updated README.md and CHANGELOG.md

Footnotes

1. Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩

[github-actions]

✅ Deploy Preview will be available once build job completes!

Name	Link
😎 Deploy Preview	https://frontdoor-test-docs.nginx.com/previews/docs/270/

---

[ADubhlaoich]

Although this is unnecessary, much like the other frontmatter fields, I kept it in as a reminder for the benefit of future documentation authors as something they may want to engage with, much like the existence of the toc field.

For future testing checks I intend to have a warning if this field does not exist, which will change to an error should the catalogue system resurface.

[mjang]

Although this is unnecessary, much like the other frontmatter fields, I kept it in as a reminder for the benefit of future documentation authors as something they may want to engage with, much like the existence of the toc field.

For future testing checks I intend to have a warning if this field does not exist, which will change to an error should the catalogue system resurface.

Cross that bridge when we come to it?