Remove External Integrations Setting Due to CDATA Package Deprecation

[sanjacornelius]

This PR removes the "External Integrations" option in the settings table, as it is no longer needed following the deprecation of the CDATA Package.

Changes

• Added a migration to remove the settings related to "External Integrations" (CDATA).

How to Test

1. Ensure the docker-executor-cdata and package-cdata are installed.
2. Confirm the "External Integrations" setting exists in the database and UI.
3. Run php artisan migrate.
4. Verify the "External Integrations" setting is removed from the database and UI.
5. Run php artisan migrate:rollback --step=1
6. Verify the "External Integrations" setting is restored in the database and UI.

Related Tickets & Packages

• FOUR-21298

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

[eiresendez]

@sanjacornelius
This deletes the records and disables the cdata section, but if the package is reinstalled via package-cdata:install, the records will return and the migration won’t be able to delete them again. We need to ensure that package-cdata and docker-executor-cdata are also removed from the composer.json before running the migration.. or Should this perhaps also be handled in this PR?