[Xcode] Don’t use a bridging header in a framework target

[lorentey]

Oops, that was not intended to work, and in fact it produces warnings in clients.

Instead, change _sa_retain_n and _sa_release_n to Swift calling convention and call them using _silgen_name trickery when in single-module configuration.

Resolves rdar://110860922

Checklist

• I've read the Contribution Guidelines
• My contributions are licensed under the Swift license.
• I've followed the coding style of the rest of the project.
• I've added tests covering all new code paths my change adds to the project (if appropriate).
• I've verified that my change does not break any existing tests.
• I've updated the documentation if necessary.

[lorentey]

@swift-ci test

[lorentey]

@swift-ci test

[glessard]

I'd recommend updating the copyright notices for the changed files, but since I also always forget to do so, I'll abstain from making a recommendation.