Remove references to objc_provider and remove force_load_direct_deps to support rules_apple > 3.15.0

[ssarad]

1. With rules_apple removing legacy objc_providers, rules_apple > 3.15.0 is no longer compatible with rules_ios due to Remove legacy Objc provider linking support bazelbuild/rules_apple#2611

2. Removing force load direct deps as its no longer needed in Bazel 7 Consider removing force_load_direct_deps_rule in Bazel 7+ #862

ERROR: /Users/ssarad/Bazel/BUILD.bazel:3:15: in apple_framework_packaging rule 
Traceback (most recent call last):
	File "/Users/ssarad/.bazel_cache/output/external/rules_ios~/rules/framework.bzl", line 1109, column 48, in _apple_framework_packaging_impl
		bundle_outs = _bundle_dynamic_framework(ctx, is_extension_safe = is_extension_safe, avoid_deps = avoid_deps)
	File "/Users/ssarad/.bazel_cache/output/external/rules_ios~/rules/framework.bzl", line 888, column 44, in _bundle_dynamic_framework
		partials.framework_provider_partial(
	File "/Users/ssarad/.bazel_cache/output/external/rules_apple~/apple/internal/partials/framework_provider.bzl", line 94, column 5, in framework_provider_partial
		def framework_provider_partial(
Error: framework_provider_partial() got unexpected keyword argument: objc_provider

This PR is attempt to make rules_ios compatible with rules_apple + remove the legacy code to force load direct deps as with Bazel 7, --incompatible_objc_alwayslink_by_default does the same thing.

[ssarad]

@luispadron If I can get your review that'd be fantastic 🙏

[luispadron]

Thanks for getting the work started here! I think theres some left-over usage:

Error: <target //tests/ios/in-tree-vendor-prebuilt-deps/Pods/MiSnap:MiSnap-MiSnap.framework-import> (rule 'apple_dynamic_framework_import') doesn't contain declared provider 'objc'

Do we need to upgrade rules_apple in MODULE.bazel, if so, we'll need to drop Bazel 6 support (probably in it's own PR).

[ssarad]

Thanks for getting the work started here! I think theres some left-over usage:

Error: <target //tests/ios/in-tree-vendor-prebuilt-deps/Pods/MiSnap:MiSnap-MiSnap.framework-import> (rule 'apple_dynamic_framework_import') doesn't contain declared provider 'objc'

Do we need to upgrade rules_apple in MODULE.bazel, if so, we'll need to drop Bazel 6 support (probably in it's own PR).

@luispadron I think when I didnt change rules_apple to 3.15.0, I got build errors that rules_apple was expecting the objc_provider parameter.

I would vote to drop Bazel 6 support mainly because

1. Your recent survey showed that most of us are on Bazel 7
2. rules_apple has dropped support for Bazel 6

What do you think? If you’d think its fine to drop support for Bazel 6, I’m happy to start that PR before we let this in.

[luispadron]

Yeah I think it makes sense! @thiagohmcruz @gyfelton FYI in case we have some reason for keeping Bazel 6

[ssarad]

Yeah I think it makes sense! @thiagohmcruz @gyfelton FYI in case we have some reason for keeping Bazel 6

Okay perfect. I can start that PR and will tag you along. I’ll likely complete it after New Years when I am back from vacation.

[ssarad]

@luispadron @jszumski

When you have some time, can I get your reviews on this PR please? All the checks should pass so its ready to review.

Thank you and much appreciated! 🙏

[thiagohmcruz]

I don't think this was being exercised in OSS properly, I'm running CI internally pointing to this PR since we rely on the features being touched here. My first test has failed with a bunch of ld: symbol(s) not found for architecture arm64. Digging more to see if it's related to this PR or not and why.

[ssarad]

I think we got all the stuffs covered here. Anything pending to merge this? @jschear @jszumski @thiagohmcruz

Thank you all again for all the reviews. I appreciate it! 🙏