Fix Swift CodeQL build collision in Analyze workflow

[Copilot]

The Analyze (swift) CodeQL job fails during xcodebuild because both app and extension targets emit colliding Swift module artifacts after CI-generated signing config stubs strip target identity. This change restores minimal target-specific xcconfig values in CI so Swift outputs are disambiguated.

• Swift CodeQL workflow fix

  • Updated .github/workflows/codeql.yml in analyze-swift → Create stub xcconfig files.
  • Replaced no-op stubs with explicit per-target values:
    • PRODUCT_MODULE_NAME
    • PRODUCT_NAME
    • PRODUCT_BUNDLE_IDENTIFIER
    • ARCHS
    • ONLY_ACTIVE_ARCH

• Collision prevention

  • Ensures ProxyBridge and extension build with distinct module metadata, preventing Multiple commands produce .../.swiftmodule/... conflicts in Release universal builds used by CodeQL.

- name: Create stub xcconfig files
  run: |
    cat > MacOS/ProxyBridge/Signing-Config-app.xcconfig << 'EOF'
    PRODUCT_MODULE_NAME = ProxyBridge
    PRODUCT_NAME = ProxyBridge
    PRODUCT_BUNDLE_IDENTIFIER = com.interceptsuite.ProxyBridge
    ARCHS = arm64 x86_64
    ONLY_ACTIVE_ARCH = NO
    EOF
    cat > MacOS/ProxyBridge/Signing-Config-ext.xcconfig << 'EOF'
    PRODUCT_MODULE_NAME = com_interceptsuite_ProxyBridge_extension
    PRODUCT_NAME = extension
    PRODUCT_BUNDLE_IDENTIFIER = com.interceptsuite.ProxyBridge.extension
    ARCHS = arm64 x86_64
    ONLY_ACTIVE_ARCH = NO
    EOF

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud