Add Exa to marketplace vetted applications

[martmull]

Adds Exa (2b7f4a2e-9c4b-4a11-b63c-2e5e7d3f5a9a) to MARKETPLACE_VETTED_APPLICATIONS at position 4, so it is marked as vetted by the marketplace catalog sync.

[Weiko]

LGTM

[twenty-ci-bot-public]

🔍 Automated Pre-Review

✅ No issues detected - This PR is ready for human review.

---

View details

Automated pre-review — human approval still required.

[greptile-apps]

Greptile Summary

This PR adds Exa to the static marketplace vetting configuration so catalog synchronization marks it as vetted.

• Adds Exa's matching universal application identifier.
• Assigns the new entry position 4, although the catalog pipeline currently ignores configured positions.

Confidence Score: 4/5

The Exa vetting change needs its ordering path fixed before merging if position 4 is part of the intended marketplace behavior.

Exa will correctly become vetted, but the synchronization path discards the newly configured position and marketplace queries do not restore that ordering.

Files Needing Attention: packages/twenty-server/src/engine/core-modules/application/application-marketplace/constants/marketplace-vetted-applications.constant.ts

Important Files Changed

Filename	Overview
packages/twenty-server/src/engine/core-modules/application/application-marketplace/constants/marketplace-vetted-applications.constant.ts	Adds the correct Exa identifier to the vetted list, but its declared position is not honored by downstream consumers.

_{Reviews (1): Last reviewed commit: "Add Exa to marketplace vetted applicatio..." | Re-trigger Greptile}

[greptile-apps]

Configured position is discarded

When the catalog synchronizes Exa, the vetting path reduces this configuration to a set of universal identifiers and marketplace queries never apply position, causing Exa's catalog placement to depend on cache iteration order instead of the configured position 4.