This fixes all remaining files and removes the todo file

Fix `user_auto_banned_email` to have the correct URLs to pages where:

- the admin can unban banned users
- the admin can update settings for auto-banning

The URLs depend on whether the user is banned from an instance or from
a namespace.

Changelog: fixed
EE: true

Our specs use static passwords, many of them are weak. This makes it
difficult to create changes which introduce password complexity
constraints.

This MR updates a small number of instances where we set weak or
hardcoded passwords, to use randomly generated passwords.

https://gitlab.com/gitlab-org/gitlab/-/issues/360030

- no longer needed

Changelog: removed

rubocop changes

- establish baseline quereis for user ids
- remove some redundant code

Changelog: performance

For SaaS, we auto-ban a user in a group when they exceed unique
project download limit set for that namespace. This version of
user_auto_banned_email (with group passed in) will be sent to group
owners when that happens.

Fixes issue where some email clients (macOS/iOS Mail.app) would
automatically turn the GitLab hostname into a link with different
styling from other links.

Also factor out some of the links in various templates' email footers,
making them more consistent between templates, and improving the
cohesion of translatable strings.

Changelog: changed

Do not allow mailers to be enqueued from
within a transaction

Changelog: fixed

For use with the feature
auto_ban_user_on_excessive_repo_downloads

Changelog: added

- to be consistent with text

Changelog: changed

Add an email tempalte that will be used to send an email to
project maintainers and owners of inactive projects.

Changelog: added

Changelog: added

Previously, Users::InProductMarketingEmail was used to track sending of
track+series (onboarding) emails. Here, we update the model to
track campaign emails (e.g. Build iOS app guide email) and track+series
(onboarding) emails.

- Fix rubocop offences

- Add specs for html and text node
- Fix N plus one queries for new review email

Changelog: performance

Merge branch 'security-sirt_2167-revert' into 'master'

See merge request gitlab-org/security/gitlab!2339

Changelog: security

The experiment has been deemed a failure so we should clean up the code
that implements it.

https://gitlab.com/gitlab-org/gitlab/-/issues/345553#note_866018518

Changelog: removed

Changelog: changed
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/351293
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/82801

Changelog: added

Changelog: added

Changelog: other

Account validation email will only be sent in EE.

When rendering Markdown in notification emails, we pass in the recipient
as current_user in the rendering context so that private references
visible to that user are rendered.

Without this change, only public references are rendered.

This also passes the issuable_reference_expansion_enabled option so that
it is rendered similar to how it is in the web UI.

Changelog: fixed

When receiving in-product marketing emails from GitLab,
a link is shown to invite members to perform specific tasks.

Changelog: added

A missing To header can cause issues with spam filters. And since we no
longer render job logs in these emails, generating these emails
individually isn't expensive anymore.

Changelog: fixed

Add Gitlab::Email::Message::InProductMarketingEmail::InviteTeam. This
email message is sent to a group creator 20 minutes after they create
the group to encourage them to invite their teammates.

When user's access request is denied and the user
has no access to read target group\project
then we shouldn't expose group\project name
in notification email.

Changelog: changed

Add an experiment for inviting members to certain
tasks from the in-product marketing emails.

Changelog: added