Create labeler for ADR updates

[trmartin4]

📔 Objective

We would like better visibility internally to opened ADRs, so that team members can offer feedback through the Github PR, without tagging the entire engineering organization as reviewers.

To distinguish these ADRs from other updates to the repo, this change will add a adr label to the PR when there are changes in the /docs/architecture/adr directory.

This label will then be used in upstream automations to trigger notifications.

⏰ 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:	1dd505b
Status:	✅  Deploy successful!
Preview URL:	https://f111af34.contributing-docs.pages.dev
Branch Preview URL:	https://add-adr-label.contributing-docs.pages.dev

View logs