Remove Microsoft Graph Configuration Caching

[sanjacornelius]

Issue & Reproduction Steps

This PR resolves an issue where Send Test Email continued to succeed even after the required Microsoft Graph configuration values (Tenant ID, Client ID, and Client Secret) were cleared.

The issue was caused by cached Microsoft Graph configuration values being used instead of the current Email Server configuration. This PR removes the configuration caching so the latest values are always used when sending emails.

Solution

• Removed configuration caching for Microsoft Graph.
• Updated the Microsoft Graph mail transport to always use the current Email Server configuration.
• Ensures missing or invalid credentials are detected immediately rather than falling back to previously cached values.

How to Test

1. Create a new Email Server using the Microsoft Graph driver.
2. Configure all required Microsoft Graph settings.
3. Send a Test Email.
4. Verify the email is sent successfully.
5. Clear the Client ID, Tenant ID, and Client Secret fields.
6. Save the Email Server configuration.
7. Send another Test Email.
8. Verify an error is displayed indicating the Microsoft Graph configuration is invalid or incomplete.

Related Tickets & Packages

• FOUR-32273

ci:connector-send-email:epic/FOUR-32115
ci:deploy

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[vladyrichter]

QA server K8S was successfully deployed https://ci-bf69eaeb90.engk8s.processmaker.net