Email modification after creation

[Zales0123]

Q	A
Bug fix?	no
New feature?	yes
BC breaks?	no
Deprecations?	no
Related tickets	it probably need this to be merged before for the green build
License	MIT

While the default configuration-based email creation is sufficient in most cases, it's not uncommon for one to need it conditional or dynamic in any other way. I thought about modifying the EmailProvider::getEmail(string $code) method to accept the array $data argument, but thought it would be more extendible to provide a set of modifiers services, that could be easily implemented in the application. Maybe it should also contain the support(EmailInterface $email): bool method, to not force checking the email code inside the modify method 🤔

Let me know what you think about such a feature 🖖 I will add some documentation to this feature if we would like to proceed with it 🫡

[GSadee]

This PR should be probably opened to 2.1 branch (which should be created as well)

[GSadee]

The base of this pull-request was changed, you need fetch and reset your local branch
if you want to add new commits to this pull request. Reset before you pull, else commits
may become messed-up.

Unless you added new commits (to this branch) locally that you did not push yet,
execute git fetch origin && git reset "email-modification-after-creation" to update your local branch.

Feel free to ask for assistance when you get stuck 👍

[GSadee]

Thank you, Mateusz! 🎉