Update docc comments for Issue.record (#1257)

Update docc comments for Issue.record

### Motivation:

Docc comments were not updated when we added a severity to Issue.record.
This fixes that.

### Modifications:

Add severity parameter to the record docc comments. 

### 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.

---------

Co-authored-by: Stuart Montgomery <[email protected]>

Author: suzannaratcliff

Sources/Testing/Issues/Issue.swift

@@ -13,7 +13,7 @@ public struct Issue: Sendable {
   /// Kinds of issues which may be recorded.
   public enum Kind: Sendable {
     /// An issue which occurred unconditionally, for example by using
-    /// ``Issue/record(_:sourceLocation:)``.
+    /// ``Issue/record(_:severity:sourceLocation:)``.
     case unconditional
 
     /// An issue due to a failed expectation, such as those produced by
@@ -409,7 +409,7 @@ extension Issue.Kind {
   @_spi(ForToolsIntegrationOnly)
   public enum Snapshot: Sendable, Codable {
     /// An issue which occurred unconditionally, for example by using
-    /// ``Issue/record(_:sourceLocation:)``.
+    /// ``Issue/record(_:severity:sourceLocation:)``.
     case unconditional
 
     /// An issue due to a failed expectation, such as those produced by

Sources/Testing/Support/CustomIssueRepresentable.swift

@@ -12,7 +12,7 @@
 /// record themselves as test issues.
 ///
 /// When a type conforms to this protocol, values of that type can be passed to
-/// ``Issue/record(_:_:)``. The testing library then calls the
+/// ``Issue/record(_:severity:sourceLocation:)``. The testing library then calls the
 /// ``customize(_:)`` function and passes it an instance of ``Issue`` that will
 /// be used to represent the value. The function can then reconfigure or replace
 /// the issue as needed.
@@ -43,7 +43,7 @@ protocol CustomIssueRepresentable: Error {
 ///
 /// This type is not part of the public interface of the testing library.
 /// External callers should generally record issues by throwing their own errors
-/// or by calling ``Issue/record(_:sourceLocation:)``.
+/// or by calling ``Issue/record(_:severity:sourceLocation:)``.
 struct SystemError: Error, CustomStringConvertible, CustomIssueRepresentable {
   var description: String
 
@@ -62,7 +62,7 @@ struct SystemError: Error, CustomStringConvertible, CustomIssueRepresentable {
 ///
 /// This type is not part of the public interface of the testing library.
 /// External callers should generally record issues by throwing their own errors
-/// or by calling ``Issue/record(_:sourceLocation:)``.
+/// or by calling ``Issue/record(_:severity:sourceLocation:)``.
 struct APIMisuseError: Error, CustomStringConvertible, CustomIssueRepresentable {
   var description: String
 

Sources/Testing/Testing.docc/MigratingFromXCTest.md

@@ -277,7 +277,7 @@ XCTest has a function, [`XCTFail()`](https://developer.apple.com/documentation/x
 that causes a test to fail immediately and unconditionally. This function is
 useful when the syntax of the language prevents the use of an `XCTAssert()`
 function. To record an unconditional issue using the testing library, use the
-``Issue/record(_:sourceLocation:)`` function:
+``Issue/record(_:severity:sourceLocation:)`` function:
 
 @Row {
   @Column {