[Issue] Move SetGuestEmailOnCart logic in a separated class

[m2-assistant]

This issue is automatically created based on existing pull request: #40395: Move SetGuestEmailOnCart logic in a separated class

---

Description (*)

This PR refactors the setGuestEmailOnCart GraphQL mutation by extracting business logic from the resolver into a dedicated model class, improving code organization and testability.

Changes

• New Model Class: Created Magento\QuoteGraphQl\Model\Cart\SetGuestEmailOnCart to handle the business logic of setting guest email on cart
• Refactored Resolver: Updated Magento\QuoteGraphQl\Model\Resolver\SetGuestEmailOnCart to delegate business logic to the new model class
• Unit Tests: Added comprehensive unit test coverage for the new model class (SetGuestEmailOnCartTest)

Motivation

The objective of this modification is to be able to more easily add logic (such as a custom control) before saving the email.

Today, the only solution is to make a beforeExecute plugin on the SetShippingMethodsOnCart class without benefiting from the controls already in place.

Manual testing scenarios (*)

Execute the graphQL setGuestEmailOnCart mutation, it must not have an error.

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Hotel]

Hello @dimitriBouteille,

Thank you for your contribution!

After going through with the issue and PR changes, it seems its good to have PR as a feature request. Hence we are moving it further as same.

Thank you