Set team-appsec as codeowners of scan.y*ml workflows

[joseph-flinn]

📔 Objective

Override the dept-devops CODEOWNERS policy for scan.y*ml files as the App Security team owns them.

⏰ 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

[github-actions]

Checkmarx One – Scan Summary & Details – b8cd67f4-2c64-4ef2-9476-b17c9fc6a2e1

No New Or Fixed Issues Found

[withinfocus]

Would be cool if this could be centralized in the new workflow linter as more of a string search or regex, perhaps for "Checkmarx" or "Sonar".

[withinfocus]

Not pursuing this. Teams will own scanning setup.