Move static packaging script into an Xcode workflow

[boundsj]

In #7773 we sidestepped an issue with packaging the iOS static build by updating the way libtool is informed about mason dependencies.

Longer term, we should move the packaging step into Xcode itself and come up with some way to test the integration of the static build in an app on CI.

cc @kkaefer @1ec5

[friedbunny]

Doing the packaging of the static framework in a script is also blocking the creation of an “iosapp-static” target in our Xcode project, which would be identical to iosapp except that it would integrate the static framework (rather than the dynamic).

[1ec5]

In #7773 we sidestepped an issue with packaging the iOS static build by updating the way libtool is informed about mason dependencies.

Is this line still relevant, now that #12808 vendors ICU instead of pulling it in through Mason?

mapbox-gl-native/platform/ios/scripts/package.sh

Line 109 in 66e95ac

`cmake -LA -N ${DERIVED_DATA} | grep MASON_PACKAGE_icu_LIBRARIES | cut -d= -f2`

[kkaefer]

Nope, let's ⛏ it

[stale]

This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions.