Well that's unfortunate, as I'd hoped the integration of swift-build would fix the various issues Xcode has with packages. This includes, but is not limited to building swift-syntax for Intel when used in macros (which was specifically called out as only fixable in SPM when moving to swift-build), building all packages for Intel on AS machines when a project has a iOS app with embedded watch target, and the inability to reliably use the same package from an iOS app and a dynamic framework embedded within that app.
More generally, I had hoped this would allow Xcode to more directly integrate with SPM, and enable things like passing build settings, especially active compilation conditions, or give Xcode direct control over how packages are built (forcing dependencies to build dynamically is often needed to fix the final issue I mentioned above). I guess these have always been Xcode limitations, which is supremely disappointing.