feat: add is_sso parameter to migration and content type handling fun…

[AishDani]

…ctions

[Copilot]

Pull request overview

This PR extends the migration/content-type creation flow to propagate an is_sso flag (so downstream calls can choose SSO access tokens vs basic authtoken auth), and refines UI-side content type mapping resolution to prefer the latest local mapping state with a Redux fallback.

Changes:

• UI: resolve mapped destination content type UID using local contentTypeMapped first, then Redux content_type_mapping, and update effect dependencies accordingly.
• API: add is_sso propagation from migration.service → fieldAttacher → contenTypeMaker → existingCtMapper token payload.
• API: include is_sso in the synthetic request payloads used to call contentMapperService for existing CT/global-field lookups.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
ui/src/components/ContentMapper/index.tsx	Updates mapping lookup logic and effect dependencies for selecting the mapped destination content type.
api/src/services/migration.service.ts	Extracts and forwards is_sso from request token payload into the migration pipeline.
api/src/utils/field-attacher.utils.ts	Accepts/forwards is_sso to content type creation.
api/src/utils/content-type-creator.utils.ts	Threads is_sso into existing content type/global field retrieval calls via token_payload.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.