Refactor "AppleAPI" into a separate repository

Tell us how we can improve Xcodes

I've been experimenting with additional tooling around Xcode Releases and, as you're aware, logging into the Apple Developer website in order to download the .xip files is quite complicated. As I was working on it, I realized that there seem to be two different implementations of AppleAPI, duplicated in XcodesOrg/XcodesApp and XcodesOrg/xcodes. The former has the better-looking API (uses the public Combine framework, can be easily hooked into custom UI, etc), but the latter is actually usable as a package dependency.

Is your feature request related to a problem? Please describe.

I would love to see AppleAPI extracted into its own repository, ideally based on the XcodesApp implementation, so that it can be used in other tools.

What would you like to see? How would you like it to work?

Some API ideas come to mind:

• don't include the Keychain code; instead have a "SecretsProvider" delegate that can read and write secure values
• Base it on Combine, to remove the need for pulling in unnecessary dependencies
• A public interface that is ObservableObject/Observable would make integration with custom UI even easier.

Compare the two AppleAPI implementations in XcodesOrg/XcodesApp and XcodesOrg/xcodes, starting with the XcodesApp version identified as having the stronger API. Define the package boundary, Combine-based public surface, and SecretsProvider replacement for Keychain; done means AppleAPI is independently consumable without unnecessary dependencies and supports the proposed UI integration.