Migrate URLs in documentation/comments/etc. from /apple/ to /swiftlang/. (#596)

This PR moves all references to URLs under https://github.com/apple/ to
https://github.com/swiftlang/.

### Checklist:

- [x] Code and documentation should follow the style of the [Style
Guide](https://github.com/apple/swift-testing/blob/main/Documentation/StyleGuide.md).
- [x] If public symbols are renamed or modified, DocC references should
be updated.

Author: grynspan

CONTRIBUTING.md

@@ -18,12 +18,12 @@ discussion prior to being accepted.
 
 To learn how to write tests using the testing library, rather than how to
 contribute to the testing library itself, see
-[Getting Started](https://github.com/apple/swift-testing/tree/main/Sources/Testing/Testing.docc/TemporaryGettingStarted.md).
+[Getting Started](https://github.com/swiftlang/swift-testing/tree/main/Sources/Testing/Testing.docc/TemporaryGettingStarted.md).
 
 ## Reporting issues
 
 Issues are tracked using the testing library's
-[GitHub Issue Tracker](https://github.com/apple/swift-testing/issues).
+[GitHub Issue Tracker](https://github.com/swiftlang/swift-testing/issues).
 
 Fill in the fields of the relevant template form offered on that page when
 creating new issues. For bug report issues, please include a minimal example
@@ -34,7 +34,7 @@ hosting service.
 ## Setting up the development environment
 
 First, clone the Swift Testing repository from
-[https://github.com/apple/swift-testing](https://github.com/apple/swift-testing).
+[https://github.com/swiftlang/swift-testing](https://github.com/swiftlang/swift-testing).
 
 If you're preparing to make a contribution, you should fork the repository first
 and clone the fork which will make opening PRs easier.
@@ -142,7 +142,7 @@ test --help` to view the usage documentation.
 
 ## Creating Pull Requests (PRs)
 
-1. Fork [https://github.com/apple/swift-testing](https://github.com/apple/swift-testing).
+1. Fork [https://github.com/swiftlang/swift-testing](https://github.com/swiftlang/swift-testing).
 1. Clone a working copy of your fork.
 1. Create a new branch.
 1. Make your code changes.

Dockerfile

@@ -9,7 +9,7 @@
 FROM swiftlang/swift:nightly-main-jammy
 
 # Set up the current build user in the same way done in the Swift.org CI system:
-# https://github.com/apple/swift-docker/blob/main/swift-ci/master/ubuntu/22.04/Dockerfile
+# https://github.com/swiftlang/swift-docker/blob/main/swift-ci/master/ubuntu/22.04/Dockerfile
 
 RUN groupadd -g 998 build-user && \
     useradd -m -r -u 998 -g build-user build-user

Documentation/CMake.md

@@ -8,7 +8,7 @@ Add Swift Testing to your project using the standard `FetchContent` or
 ```cmake
 include(FetchContent)
 FetchContent_Declare(SwiftTesting
-  GIT_REPOSITORY https://github.com/apple/swift-testing.git
+  GIT_REPOSITORY https://github.com/swiftlang/swift-testing.git
   GIT_TAG main)
 FetchContent_MakeAvailable(SwiftTesting)
 ```

Documentation/Proposals/0000-proposal-template.md

@@ -3,10 +3,10 @@
 * Proposal: [SWT-NNNN](NNNN-filename.md)
 * Authors: [Author 1](https://github.com/author1), [Author 2](https://github.com/author2)
 * Status: **Awaiting implementation** or **Awaiting review**
-* Bug: _if applicable_ [apple/swift-testing#NNNNN](https://github.com/apple/swift-testing/issues/NNNNN)
-* Implementation: [apple/swift-testing#NNNNN](https://github.com/apple/swift-testing/pull/NNNNN)
+* Bug: _if applicable_ [swiftlang/swift-testing#NNNNN](https://github.com/swiftlang/swift-testing/issues/NNNNN)
+* Implementation: [swiftlang/swift-testing#NNNNN](https://github.com/swiftlang/swift-testing/pull/NNNNN)
 * Previous Proposal: _if applicable_ [SWT-XXXX](XXXX-filename.md)
-* Previous Revision: _if applicable_ [1](https://github.com/apple/swift-testing/blob/...commit-ID.../Documentation/Proposals/NNNN-filename.md)
+* Previous Revision: _if applicable_ [1](https://github.com/swiftlang/swift-testing/blob/...commit-ID.../Documentation/Proposals/NNNN-filename.md)
 * Review: ([pitch](https://forums.swift.org/...))
 
 When filling out this template, you should delete or replace all of the text
@@ -146,7 +146,7 @@ the current proposal. It's important to make focused, self-contained proposals
 that can be incrementally implemented and reviewed, but it's also good when
 proposals feel "complete" rather than leaving significant gaps in their design.
 An an example from the Swift project, when
-[SE-0193](https://github.com/apple/swift-evolution/blob/main/proposals/0193-cross-module-inlining-and-specialization.md)
+[SE-0193](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0193-cross-module-inlining-and-specialization.md)
 introduced the `@inlinable` attribute, it also included the `@usableFromInline`
 attribute so that declarations used in inlinable functions didn't have to be
 `public`. This was a relatively small addition to the proposal which avoided

Documentation/Proposals/0001-refactor-bug-inits.md

@@ -3,7 +3,7 @@
 * Proposal: [SWT-0001](0001-refactor-bug-inits.md)
 * Authors: [Jonathan Grynspan](https://github.com/grynspan)
 * Status: **Accepted**
-* Implementation: [apple/swift-testing#401](https://github.com/apple/swift-testing/pull/401)
+* Implementation: [swiftlang/swift-testing#401](https://github.com/swiftlang/swift-testing/pull/401)
 * Review: ([pitch](https://forums.swift.org/t/pitch-dedicated-bug-functions-for-urls-and-ids/71842)), ([acceptance](https://forums.swift.org/t/swt-0001-dedicated-bug-functions-for-urls-and-ids/71842/2))
 
 ## Introduction

Documentation/Proposals/0002-json-abi.md

@@ -3,8 +3,8 @@
 * Proposal: [SWT-0002](0002-json-abi.md)
 * Authors: [Jonathan Grynspan](https://github.com/grynspan)
 * Status: **Accepted**
-* Implementation: [apple/swift-testing#383](https://github.com/apple/swift-testing/pull/383),
-  [apple/swift-testing#402](https://github.com/apple/swift-testing/pull/402)
+* Implementation: [swiftlang/swift-testing#383](https://github.com/swiftlang/swift-testing/pull/383),
+  [swiftlang/swift-testing#402](https://github.com/swiftlang/swift-testing/pull/402)
 * Review: ([pitch](https://forums.swift.org/t/pitch-a-stable-json-based-abi-for-tools-integration/72627)), ([acceptance](https://forums.swift.org/t/pitch-a-stable-json-based-abi-for-tools-integration/72627/4))
 
 ## Introduction

Documentation/Proposals/0003-make-serialized-trait-api.md

@@ -4,7 +4,7 @@
 * Authors: [Dennis Weissmann](https://github.com/dennisweissmann)
 * Status: **Accepted**
 * Implementation: 
-[apple/swift-testing#535](https://github.com/apple/swift-testing/pull/535)
+[swiftlang/swift-testing#535](https://github.com/swiftlang/swift-testing/pull/535)
 * Review: 
 ([pitch](https://forums.swift.org/t/pitch-make-serialized-trait-public-api/73147)),
 ([acceptance](https://forums.swift.org/t/pitch-make-serialized-trait-public-api/73147/5))

Documentation/Proposals/0004-constrain-the-granularity-of-test-time-limit-durations.md

@@ -5,7 +5,7 @@
 * Authors: [Dennis Weissmann](https://github.com/dennisweissmann)
 * Status: **Accepted**
 * Implementation: 
-[apple/swift-testing#534](https://github.com/apple/swift-testing/pull/534)
+[swiftlang/swift-testing#534](https://github.com/swiftlang/swift-testing/pull/534)
 * Review: 
 ([pitch](https://forums.swift.org/t/pitch-constrain-the-granularity-of-test-time-limit-durations/73146)),
 ([acceptance](https://forums.swift.org/t/pitch-constrain-the-granularity-of-test-time-limit-durations/73146/3))

Documentation/README.md

@@ -13,36 +13,36 @@ See https://swift.org/CONTRIBUTORS.txt for Swift project authors
 ## API and usage guides
 
 The detailed documentation for Swift Testing can be found on the
-[Swift Package Index](https://swiftpackageindex.com/apple/swift-testing/main/documentation/testing).
+[Swift Package Index](https://swiftpackageindex.com/swiftlang/swift-testing/main/documentation/testing).
 There, you can delve into comprehensive guides, tutorials, and API references to
 make the most out of this package.
 
-This documentation is generated using [DocC](https://github.com/apple/swift-docc)
+This documentation is generated using [DocC](https://github.com/swiftlang/swift-docc)
 and is derived from symbol documentation in this project's source code as well
 as supplemental content located in the
-[`Sources/Testing/Testing.docc/`](https://github.com/apple/swift-testing/tree/main/Sources/Testing/Testing.docc)
+[`Sources/Testing/Testing.docc/`](https://github.com/swiftlang/swift-testing/tree/main/Sources/Testing/Testing.docc)
 directory.
 
 ## Vision document
 
-The [Vision document](https://github.com/apple/swift-evolution/blob/main/visions/swift-testing.md)
+The [Vision document](https://github.com/swiftlang/swift-evolution/blob/main/visions/swift-testing.md)
 for Swift Testing offers a comprehensive discussion of the project's design
 principles and goals. 
 
 ## Development and contribution
 
-- The top-level [`README`](https://github.com/apple/swift-testing/blob/main/README.md)
+- The top-level [`README`](https://github.com/swiftlang/swift-testing/blob/main/README.md)
   gives a high-level overview of the project, shows current CI status, lists the
   support status of various platforms, and more.
-- [Contributing](https://github.com/apple/swift-testing/blob/main/CONTRIBUTING.md)
+- [Contributing](https://github.com/swiftlang/swift-testing/blob/main/CONTRIBUTING.md)
   provides guidance for developing and making project contributions.
-- [Style Guide](https://github.com/apple/swift-testing/blob/main/Documentation/StyleGuide.md)
+- [Style Guide](https://github.com/swiftlang/swift-testing/blob/main/Documentation/StyleGuide.md)
   describes this project's guidelines for code and documentation style.
-- [SPI groups in Swift Testing](https://github.com/apple/swift-testing/blob/main/Documentation/SPI.md)
+- [SPI groups in Swift Testing](https://github.com/swiftlang/swift-testing/blob/main/Documentation/SPI.md)
   describes when and how the testing library uses Swift SPI.
 
 ## Project maintenance
 
-- The [Releases](https://github.com/apple/swift-testing/blob/main/Documentation/Releases.md)
+- The [Releases](https://github.com/swiftlang/swift-testing/blob/main/Documentation/Releases.md)
   document describes the process of creating and publishing a new release of
   Swift Testing — a task which may be performed by project administrators.

Documentation/Releases.md

@@ -49,8 +49,8 @@ be updated so that the release can be used as a package dependency:
    update the line:
 
     ```diff
-    -  .package(url: "https://github.com/apple/swift-testing.git", branch: "main"),
-    +  .package(url: "https://github.com/apple/swift-testing.git", from: "x.y.z"),
+    -  .package(url: "https://github.com/swiftlang/swift-testing.git", branch: "main"),
+    +  .package(url: "https://github.com/swiftlang/swift-testing.git", from: "x.y.z"),
     ```
 
 The repository's local state is now updated. To commit it to your branch, run
@@ -94,7 +94,7 @@ git tag x.y.z
 git push -u origin x.y.z
 ```
 
-The release is now live and publicly visible [here](https://github.com/apple/swift-testing/tags).
+The release is now live and publicly visible [here](https://github.com/swiftlang/swift-testing/tags).
 Developers using Swift Package Manager and listing Swift Testing as a dependency
 will automatically update to it.