Allow --experimental_strict_conflict_checks to pass for XCFramework slices

[mattrobmattrob]

Repro: #671

$ bazel build //Lib --apple_platform_type=ios
INFO: Build option --features has changed, discarding analysis cache.
ERROR: One of the output paths 'bazel-out/ios-sim_arm64-min9.0-applebin_ios-ios_sim_arm64-fastbuild-ST-c68d53a6ad5a/bin/external/_main~non_module_deps~com_github_krzyzanowskim_cryptoswift/CryptoSwift.import_middleman/CryptoSwift.framework' (belonging to @_main~non_module_deps~com_github_krzyzanowskim_cryptoswift//:CryptoSwift.import_middleman) and 'bazel-out/ios-sim_arm64-min9.0-applebin_ios-ios_sim_arm64-fastbuild-ST-c68d53a6ad5a/bin/external/_main~non_module_deps~com_github_krzyzanowskim_cryptoswift/CryptoSwift.import_middleman/CryptoSwift.framework/CryptoSwift' (belonging to @_main~non_module_deps~com_github_krzyzanowskim_cryptoswift//:CryptoSwift.import_middleman) is a prefix of the other. These actions cannot be simultaneously present; please rename one of the output files or build just one of them
ERROR: com.google.devtools.build.lib.actions.ArtifactPrefixConflictException: One of the output paths 'bazel-out/ios-sim_arm64-min9.0-applebin_ios-ios_sim_arm64-fastbuild-ST-c68d53a6ad5a/bin/external/_main~non_module_deps~com_github_krzyzanowskim_cryptoswift/CryptoSwift.import_middleman/CryptoSwift.framework' (belonging to @_main~non_module_deps~com_github_krzyzanowskim_cryptoswift//:CryptoSwift.import_middleman) and 'bazel-out/ios-sim_arm64-min9.0-applebin_ios-ios_sim_arm64-fastbuild-ST-c68d53a6ad5a/bin/external/_main~non_module_deps~com_github_krzyzanowskim_cryptoswift/CryptoSwift.import_middleman/CryptoSwift.framework/CryptoSwift' (belonging to @_main~non_module_deps~com_github_krzyzanowskim_cryptoswift//:CryptoSwift.import_middleman) is a prefix of the other. These actions cannot be simultaneously present; please rename one of the output files or build just one of them
INFO: Elapsed time: 0.478s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (22 packages loaded, 3611 targets configured)

[jszumski]

Background: bazelbuild/bazel#16729

It looks like this is expected to be a breaking change in Bazel 7.0