Facebook schemes pollute Xcode via SPM

### Checklist before submitting a bug report

- [X] I've updated to the latest released version of the SDK
- [X] I've searched for existing [GitHub issues](https://github.com/facebook/facebook-ios-sdk/issues)
- [X] I've looked for existing answers on [Stack Overflow](https://facebook.stackoverflow.com), the [Facebook Developer Community Forum](https://developers.facebook.com/community/) and the [Facebook Developers Group](https://www.facebook.com/groups/fbdevelopers)
- [X] I've read the [Code of Conduct](https://github.com/facebook/facebook-ios-sdk/blob/main/CODE_OF_CONDUCT.md)
- [X] This issue is not security related and can safely be disclosed publicly on GitHub

### Xcode version

16.1.0

### Facebook iOS SDK version

17.4.0

### Dependency Manager

SPM

### SDK Framework

Core

### Goals

Move the schemes [from here](https://github.com/facebook/facebook-ios-sdk/tree/main/.swiftpm/xcode/xcshareddata/xcschemes) into the workspace to avoid polluting scheme list for developers. This may be an Xcode oversight but I'd bet it's also an oversight from Facebook and a few other repos.

### Expected results

The Facebook and FBSDKCoreKit schemes shouldn't show for client developer Xcodes.

### Actual results

Facebook and FBSDKCoreKit schemes keep being added by Xcode to the list of available schemes which is a pain when working with lots of dependencies with similar problem with multiple targets.

### Steps to reproduce

Add Facebook via SPM to any project. See [this discussion](https://forums.developer.apple.com/forums/thread/716024) for more information.

### Code samples & details

_No response_