Luis Padron

`toolchain_attrs` was removed from `swift_common` [here](https://github.com/bazelbuild/rules_swift/commit/eb2a7ff8312a0b37837836314e372af357b4764a), ensure you are using a rules_swift that is compatible with rules_apple.

> Personally, it feels like we should provide some way to execute this step via Bazel. It helps ensure that the swift package resolve/update use the same version of Swift...

Does SPM always link as well, e.g. when doing something like `swift build`?

@brentleyjones @keith I rebased this and added checks for the bazel feature that's required. Mind taking a look?

FWIW in our Cash App code we ran into dynamic framework paths being the root cause of crashes when loading bundles. A lot of code assumes `Bundle.main` (or equivalent) is...

This is what we updated our resource bundle generator stencil to look like: ```swift import Foundation extension Bundle { private final class {{param.moduleName}}Sentinel {} @objc({{param.lowerCamelCaseModuleName}}ResourcesBundle) {{param.accessLevel}} static var {{param.lowerCamelCaseModuleName}}Resources: Bundle...