Establish release process for Turf binary distribution

[aleksproger]

• Distribute Turf as xcframework in SwiftPM and CocoaPods
• Create release and pre-release scripts to fully automate release process
• Build from source using xcodebuild instead of SwiftPM
• Delete jobs for building on Linux and separete job for building with library evolution
• Add create xcframework job on PRs

Issues solved:

• Clients that depend on source-based Turf and MapboxSDK stack won't receive two copies ob library in SwiftPM, compatibility will be ensured by SwiftPM

[1ec5]

Out of curiosity, could you speak to why this library is no longer being distributed as source code and no longer supporting Linux?

[aleksproger]

@1ec5, Turf will become a dependency of other Mapbox library deeper in Mapbox SDK stack and this library is distributed as binary only dynamic framework, which means that Turf needs to be distributed as binary as well. In order to eliminate the issues when client may depend on Mapbox SDK stack where binary dependency exists and also on source-based Turf it was decided to switch to binary distribution of Turf and allow SwiftPM properly resolve compatibility issues. Technically, the support for Linux is not dropped, however it was only in SwiftPM and now we don't build with SwiftPM, but use .xcframework binary instead.

[aleksproger]

@1ec5 according to your question we came up with the solution to continue support for Linux with source based build, while Apple platforms will use binary distribution compatible with Mapbox SDK stack