`mp dev-env pull integration` silently fails to deconstruct integrations when pulling items with UUIDs

[hzmndt-debug]

Description
When pulling a custom integration from the SecOps environment using mp dev-env pull integration <IntegrationName>, the pulled zip file name includes a UUID (e.g., CaseFederation__cf77f51a-0ffb-43bb-ab14-e6ff7c4f0a8d.zip) and extracts to a similarly named folder.
During the deconstruct phase, the mp CLI's is_integration function checks if the folder corresponds to a valid integration by looking for a .def file matching the folder name (e.g., Integration-CaseFederation__cf77f51a-0ffb-43bb-ab14-e6ff7c4f0a8d.def).

However, the internal .def file is simply named Integration-CaseFederation.def. Because the filenames do not match due to the UUID suffix, the validation fails. As a result, the mp tool silently skips extracting and deconstructing the integration, leaving the destination directory completely empty despite outputting a success message.

Steps to Reproduce

1. Have a custom integration deployed in Google SecOps (e.g., CaseFederation).
2. 2. Run mp dev-env pull integration CaseFederation__<UUID>.
3. 3. Notice that the command outputs a success message, but the target destination directory is empty.
4. 4. Using the --keep-zip flag shows that the zip downloads correctly, but the deconstruct process aborts because the UUID suffix in the folder name doesn't match the .def file name.
      Expected Behavior
      The pull command should successfully download, extract, and deconstruct the integration into the destination folder.

[AmitJ98]

Hey @hzmndt-debug
What is the Integration name in SecOps idea? CaseFederation or CaseFederation_UUID
can you share a screen shot or the custom integration?

[doriaviram]

Closing until we will have a more clarity about the issue