Add replyTo field to SendGrid provider and Email type

[hannesortmeier]

Description

This PR introduces the following changes:

Add optional replyTo field to Email type (commit 7ddc034): This commit adds a new optional field replyTo to the Email type. This allows for specifying a different email address that recipients will reply to.

Add optional replyTo field to SendGrid provider (commit adae95b): This commit extends the SendGrid provider to support the new replyTo field. If provided, the SendGrid provider will use this field as the reply-to address in the emails it sends.

Document replyTo field for SendGrid provider (commit 1120fae): This commit adds documentation for the new replyTo field in the SendGrid provider. This helps to ensure that the usage of this new field is clear to other developers.

These changes provide more flexibility in handling replies to emails sent by the application since without the replyTo field set, replying to an E-Mail sent by SendGrid will result in a 550 Mailbox not found.

Select what type of change this PR introduces:

1. Just code/docs improvement (no functional change).
2. Bug fix (non-breaking change which fixes an issue).
3. New feature (non-breaking change which adds functionality).
4. Breaking change (fix or feature that would cause existing functionality to not work as expected).

Update Waspc ChangeLog and version if needed

If you did a bug fix, new feature, or breaking change, that affects waspc, make sure you satisfy the following:

1. I updated ChangeLog.md with description of the change this PR introduces.
2. I bumped waspc version in waspc.cabal to reflect changes I introduced, with regards to the version of the latest wasp release, if the bump was needed.

[infomiho]

I can see that your forked main branch is 33 commits behind the main in our repo.

We are now working on 0.14.0 and you'll see the entries in the Changelog once you sync your branch with the main repo.

[infomiho]

Did you analyze the other providers to see if they also provide options for replyTo field? We need to consider the SMTP and the Mailgun providers to make sure Wasp works for as many people as possible.

[hannesortmeier]

I only checked the Mailgun provider which does not offer a reply_to option. I'm pretty sure, that it can be implemented for the SMTP provider as well. I will have a look at it.

[infomiho]

Let's remove this indent change to keep the changeset minimal.

[hannesortmeier]

Whoops, formatters at work I guess.

[infomiho]

Nice job! Thanks for the contribution.

There are couple of things we need to do before we can merge this:

• make sure your fork has the latest changes from main https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-branch-from-the-web-ui
• update the Changelog not to mention 0.13.3 since this is not a version we'll be releasing. Instead, you should append your changes under the 0.14.0
• you should investigate if the Mailgun or SMTP providers can also use the replyTo option and use it for them as well
• update the docs accordingly (related to the previous point)
• update the e2e tests (this might be tricky for you if you didn't set up the Haskell toolchain locally)
• ensure the feature works by testing it locally with the examples/todoApp (again, this might be tricky for you if you didn't set up the project locally)

[infomiho]

Closed by accident!