fix: sender rules have to apply on user and its aliases

[guillaumedc]

Related issue(s)

#554

How to test manually

• on main:
  • Authorize/ban senders for an account email
  • Create an alias for this account
  • Go to Authorized senders
  • The authorized/banned senders are applied only to the base account, not the alias
• on this branch:
  • Authorize/ban senders for an account email
  • Create an alias for this account
  • Go to Authorized senders
  • The authorized/banned senders are applied to the base account and the alias

Reviewer checklist

• Code is manually tested
• Interface works on both mobiles and big screens
• Interface works on both Firefox and Chrome
• Tests are up to date
• Documentation is up to date
• Pull request has been reviewed and approved

[github-actions]

Test Results

18 tests   18 ✅  6s ⏱️
 4 suites   0 💤
 1 files     0 ❌

Results for commit b7d464f.

♻️ This comment has been updated with latest results.

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}