fix: prevent affiliations for project-registry member organizations

[skwowet]

Summary

Git integration was creating project-registry member organizations and segment affiliations without respecting org-level isAffiliationBlocked. This prevents those incoming affiliations from being treated as allowed on blocked organizations.

Changes

• Add fetch_organizations to read isAffiliationBlocked for org ids in a batch
• Return newly inserted member organization rows from insert_member_organizations
• Add insert_member_organization_affiliation_overrides for allowAffiliation=false overrides
• In apply_affiliations, resolve blocked orgs from all resolved stints
• Skip memberSegmentAffiliations inserts for blocked organizations
• Insert affiliation overrides for newly created member organizations on blocked organizations

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.