ADR for integration identification

[withinfocus]

🎟️ Tracking

Originated from bot management discussions amongst leadership.

📔 Objective

ADR to enhance our server request pipeline with additional validations and registration of integrations.

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation
  team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed
  issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[cloudflare-workers-and-pages]

Deploying contributing-docs with    Cloudflare Pages

Latest commit:	5e255fc
Status:	✅  Deploy successful!
Preview URL:	https://5e7cd4c6.contributing-docs.pages.dev
Branch Preview URL:	https://integrations.contributing-docs.pages.dev

View logs

[github-actions]

Checkmarx One – Scan Summary & Details – ef7a075a-1406-4fbc-bc47-9cb49ccea64f

No New Or Fixed Issues Found

[MGibson1]

My biggest concern here is there is nothing in place or specified here that will keep us honest in the future. I DO NOT want a system by which we can throttle alternative clients to the point of uselessness.