WPB-19804 Email template validation

[battermann]

https://wearezeta.atlassian.net/browse/WPB-19804

Checklist

• Add a new entry in an appropriate subdirectory of changelog.d
• Read and follow the PR guidelines

[Copilot]

Pull request overview

This PR adds comprehensive validation for email templates used in team and user communications, while refactoring the email rendering system to make it more testable and removing unused SMS/call templates.

Changes:

• Added integration tests to validate all email templates render correctly without variable replacement errors
• Refactored email rendering to use a testable polysemy-based approach with error tracking
• Removed deprecated SMS and call templates across all locales
• Updated URLs in configuration files to use new, more user-friendly formats

Reviewed changes

Copilot reviewed 153 out of 153 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
services/brig/test/integration/API/Template.hs	New test module validating email template rendering for teams and users
libs/wire-subsystems/src/Wire/EmailSubsystem/Interpreter.hs	Refactored to use polysemy Output effect for tracking unreplaced variables
libs/wire-subsystems/src/Wire/EmailSubsystem/Template.hs	Added new rendering functions with error tracking capabilities
libs/wire-subsystems/src/Wire/EmailSubsystem/Templates/*.hs	Split template definitions into separate User and Team modules
services/brig/src/Brig/Template.hs	Added genTemplateBrandingMap for Map-based branding replacement
services/brig/brig.integration.yaml	Updated URLs to use cleaner, more user-friendly formats
services/brig/src/Brig/Team/Email.hs	Deleted - functionality moved to EmailSubsystem
libs/wire-subsystems/templates//user/sms/	Removed SMS templates across all locales
libs/wire-subsystems/templates//user/call/	Removed call templates across all locales
libs/wire-subsystems/templates//team/email/new-creator-welcome	Removed creator welcome templates

Comments suppressed due to low confidence (2)

services/brig/test/integration/API/Template.hs:1

• The hardcoded URL in the test assertion should match the configuration in brig.integration.yaml. Consider extracting the base URL and path pattern to avoid inconsistencies between test expectations and actual configuration.
  services/brig/test/integration/API/Template.hs:1
• Similar to the previous comment, this hardcoded URL should align with the configuration. Consider using a shared constant or configuration value to ensure consistency.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.