Add --use-static-frameworks lint option

[paulb777]

Also fix a bad merge in the CHANGELOG.md

[paulb777]

Rebased

[dnkoutso]

I continue to feel that the proliferation of these options is making things much worse for maintainers imo but I don't see a clear way on how to manage this effectively.

Basically an author can now publish a pod under very specific set of options (modular headers, use libraries and now static frameworks) which means a consumer of a pod must somehow know that the pod works only works in a very specific way.

None of this information is transcribed or communicated anywhere right now.

Do you have any thoughts or ideas about this?

[paulb777]

@dnkoutso I'd be fine to remove the option from push.

The reason I want this option is that the boat has already sailed on these options available in Podfile's and it would be a nice for authors to have an easy way to set up CI to test all the options before publishing.

Specifically, I'd like to use it here for example - https://github.com/firebase/firebase-ios-sdk/blob/master/.github/workflows/storage.yml#L95

[amorde]

I agree with @dnkoutso on the proliferation of options but I think we've somewhat designed ourselves into a corner here, and without these options the lint commands become much less useful

[amorde]

is this correct?

[paulb777]

Yes, #9392 is in master and not 1.9.1