Code-generate runtime styling portion of umbrella header

[1ec5]

Per #5727 (comment), it’s a bit of a chore to keep the umbrella header up-to-date. We should break out the runtime styling imports into a separate, code-generated header and include that header. MapKit’s umbrella header is modularized like this too. We’ll need to make sure jazzy can follow the imports and all the supported build configurations continue to work all the way through to App Store validation.

/cc @frederoni @friedbunny

[1ec5]

Not critical. Moving off the v3.4.1 milestone.

[1ec5]

We can also have the runtime styling generating code add any new runtime styling files to the Xcode project using the xcode npm package. That’ll take care of most of the manual steps to adding a new layer or source type. On the other hand, that doesn’t happen very frequently.

/cc @kkaefer

[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.