Proposal to remove unsafe-skip-xcode-version-check

[ravimandala]

Bluepill releases support a specific Xcode version and there might be unforeseen issues when used with a different Xcode version. For this reason, a config flag named unsafe-skip-xcode-version-check was introduced. When this config is set it would skip the Xcode version check so that Bluepill can be used with Xcode versions other than the one that is officially supported.

However, the check is not very valuable and could often times confuse to the developers. How about removing the check while somehow continuing to indicate which Xcode versions are supported by specific Bluepill versions? \cc @ob

[acecilia]

What about when bluepill supports Xcode 13.1 but your project uses Xcode 13.2.1? What should happen in such case?

[ob]

I think the rationale is that a given version of bluepill might support more than a given Xcode version. Ideally we'd have a testing matrix with a few modern versions of Xcode and avoid tying bluepill to a single version. We could try to set up a matrix in CI and see if that's really the case.