[InAppMessaging] Consolidate FIAM and FIAMSwift

[ncooke3]

Context

• The contents of FIAM's Swift extension SDK has been moved into the main FIAM module, and the FIAM Swift extension SDK now re-exports the API that used to live in it.
• This change should be non-breaking.

---

Tasks

• The affected extension podspecs should be versioned to pin to the releasing version.
• When this PR is merged, stage the affected podspecs and notify the Games team.

---

Important

• This PR contains an assumption in the source code that docs will be at hosted at https://firebase.google.com/docs/ios/swift-migration cc: @morganchen12

[google-oss-bot]

Coverage Report ¹

Affected Products

• FirebaseInAppMessaging-iOS-FirebaseInAppMessaging.framework

  Overall coverage changed from 46.22% (1e0f294) to 44.72% (3935dea) by -1.50%.

  Filename	Base (1e0f294)	Merge (3935dea)	Diff
  CustomInAppMessageDisplayViewModifier.swift	?	0.00%	?
  SwiftUIPreviewHelpers.swift	?	0.00%	?

Test Logs

• Base (1e0f294): https://github.com/firebase/firebase-ios-sdk/actions/runs/6498872977
• Merge (3935dea): https://github.com/firebase/firebase-ios-sdk/actions/runs/6501220204

1. https://storage.googleapis.com/firebase-sdk-metric-reports/UZQrhBx8nN.html

[google-oss-bot]

Size Report ¹

Affected Products

• FirebaseInAppMessaging

  Type	Base (0c9fe27)	Merge (4e1a0f3)	Diff
  CocoaPods	?	-51.5 kB	? (?)

Test Logs

• Merge (4e1a0f3): https://github.com/firebase/firebase-ios-sdk/actions/runs/6175234712

1. https://storage.googleapis.com/firebase-sdk-metric-reports/k4wfQbBowr.html

[ncooke3]

Closed and re-opened to deflate some transient network failures in CI.

[ncooke3]

I'm a bit unsure of how to fix spectesting / specs_testing (FirebaseInAppMessagingSwift.podspec) (pull_request).

After reproducing locally, it seems that the FirebaseInAppMessagingSwift.podspec's dependency on FirebaseInAppMessaging.podspec isn't coming from the FirebaseInAppMessagingSwift.podspec that has been modified in this PR! Therefore, FirebaseInAppMessagingSwift.podspec doesn't lint successfully because it really needs the updated FirebaseInAppMessaging.podspec that is also changed in this PR.

I'm able to get things linting successfully if I lint the specs together:

pod spec lint FirebaseInAppMessagingSwift.podspec FirebaseInAppMessaging.podspec --platforms=ios --skip-tests --allow-warnings --sources=https://github.com/firebase/SpecsTesting,https://cdn.cocoapods.org/

I'd imagine this should workflow failure may happen anytime multiple specs are updated in a single PR where the changes are heavily dependent.

Is this considered a bug in the workflow? Should the workflow lint all changed specs together rather than breaking them up into a job matrix where each spec is linted separately?

[paulb777]

It's a known issue we've seen before. Historically, we've ignored interdependent spectesting issues like this until after merging and updating tags.

Let's discuss next week

[paulb777]

May also want to notify @mikehardy when the consolidation podspecs are staged.