fix: segment compatibility

[Shahroz16]

Problem:
Our fork and Segment SDK can't be added at the same time via SPM.

Solution:
Update module name from Segment to CioAnalytics.

Changes:

• Package.json for updated module name
• Podspec for updated module name
• External Module reference of Segment
• Sample Apps
• Objc symbols to avoid linker issues because of same objc names

[PaulWen]

Hi @Shahroz16, I just tried to upgrade from CIO 2x to CIO 3x but I am now blocked as we already have the Segment SDK in place and can't add this library at the same time via SPM.

Two questions:

1. What does CIO use this library for?
2. When is this PR expected to be merged or is there any alternative way to upgrade to CIO 3x while also having the Segment SDK installed via SPM?

Thanks!

[Shahroz16]

Hey @PaulWen, thank you for your feedback. As customerio/customerio-ios#670, we are currently evaluating the effort required to support both SDKs running in parallel, but we haven't finalized a solution yet.

In the meantime, you can continue using V2, as it is fully supported and compatible with analytics-swift SDK. We will keep you updated on any developments.

Since V3 offers support for our CDP, we utilize features of Segment SDK. If you have any additional feedback or more use cases to share regarding the integration of analytics-swift SDK with V3 (as in our using both CIO CDP and Segment or just wanted to utilize some of v2 features of CIO), please do share with us. If it's easier to share privately you can email product@customer.io to start a thread with our product team.

[mrehan27]

Looks good 👍🏻