feat: add reply_to to helpers.Mail

[vindarel]

Fixes

Add the reply_to keyword argument to helpers.mail.Mail.

Otherwise, we must create the Mail and then set the reply_to with
its setter (and we have to dig the repository to find out).

I didn't run the tests locally.

Checklist

• I acknowledge that all my contributions will be made under the project's license
• I have made a material change to the repo (functionality, testing, spelling, grammar)
• I have read the Contribution Guidelines and my PR follows them
• I have titled the PR appropriately
• I have updated my branch with the main branch
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation about the functionality in the appropriate .md file
• I have added inline documentation to the code I modified

[vindarel]

helper-runner_1_f23ff83f7e70 | Ran 339 tests in 29.286s

helper-runner_1_f23ff83f7e70 | 

helper-runner_1_f23ff83f7e70 | OK

helper-runner_1_f23ff83f7e70 | <MagicMock name='Client().post().status_code' id='140154951636560'>

helper-runner_1_f23ff83f7e70 | <MagicMock name='Client().post().headers' id='140154951158992'>

helper-runner_1_f23ff83f7e70 | <MagicMock name='Client().post().body' id='140154951226704'>

helper-runner_1_f23ff83f7e70 | {}

prism_helper-runner_1_f23ff83f7e70 exited with code 0

Aborting on container exit...

Stopping prism_nginx_1_d5c65d2ecb6e         ... 

Stopping prism_prism_1_df1f6f32c7e1         ... 

The command "make test-docker" exited with 0.

yay o/

[shwetha-manvinkurke]

Thanks for the contribution!

[shwetha-manvinkurke]

@vindarel need to revert this change since

• this breaks for the current users
• reply_to is a little redundant here

Recommend just using the setter.