Bump scalafmt (#465)

.scalafmt.conf

@@ -1,4 +1,4 @@
-version = "3.3.0"
+version = "3.6.1"
 runner.dialect = scala213
 fileOverride {
   "glob:**/src/main/scala-3/**" {

aws-sdk-v2/services/acmpca/src/main/scala/facade/amazonaws/services/ACMPCA.scala

@@ -443,7 +443,7 @@ package object acmpca {
   }
 
   /** Contains configuration information for a certificate revocation list (CRL). Your private certificate authority (CA) creates base CRLs. Delta CRLs are not supported. You can enable CRLs for your new or an existing private CA by setting the ```Enabled``` parameter to <code>true</code>. Your private CA writes CRLs to an S3 bucket that you specify in the ```S3BucketName``` parameter. You can hide the name of your bucket by specifying a value for the ```CustomCname``` parameter. Your private CA copies the CNAME or the S3 bucket name to the ```CRL Distribution Points``` extension of each certificate it issues. Your S3 bucket policy must give write permission to ACM Private CA. ACM Private CA assets that are stored in Amazon S3 can be protected with encryption. For more information, see [[https://docs.aws.amazon.com/acm-pca/latest/userguide/PcaCreateCa.html#crl-encryption|Encrypting Your CRLs]]. Your private CA uses the value in the ```ExpirationInDays``` parameter to calculate the
-    * ```nextUpdate``` field in the CRL. The CRL is refreshed at 1/2 the age of next update or when a certificate is revoked. When a certificate is revoked, it is recorded in the next CRL that is generated and in the next audit report. Only time valid certificates are listed in the CRL. Expired certificates are not included. A CRL is typically updated approximately 30 minutes after a certificate is revoked. If for any reason a CRL update fails, ACM Private CA makes further attempts every 15 minutes. CRLs contain the following fields: * ```Version```: The current version number defined in RFC 5280 is V2. The integer value is 0x1. * ```Signature Algorithm```: The name of the algorithm used to sign the CRL. * ```Issuer```: The X.500 distinguished name of your private CA that issued the CRL. * ```Last Update```: The issue date and time of this CRL. * ```Next Update```: The day and time by which the next CRL will be issued. * ```Revoked Certificates```: List of revoked certificates. Each
+    * \```nextUpdate``` field in the CRL. The CRL is refreshed at 1/2 the age of next update or when a certificate is revoked. When a certificate is revoked, it is recorded in the next CRL that is generated and in the next audit report. Only time valid certificates are listed in the CRL. Expired certificates are not included. A CRL is typically updated approximately 30 minutes after a certificate is revoked. If for any reason a CRL update fails, ACM Private CA makes further attempts every 15 minutes. CRLs contain the following fields: * ```Version```: The current version number defined in RFC 5280 is V2. The integer value is 0x1. * ```Signature Algorithm```: The name of the algorithm used to sign the CRL. * ```Issuer```: The X.500 distinguished name of your private CA that issued the CRL. * ```Last Update```: The issue date and time of this CRL. * ```Next Update```: The day and time by which the next CRL will be issued. * ```Revoked Certificates```: List of revoked certificates. Each
     * list item contains the following information. <li> ```Serial Number```: The serial number, in hexadecimal format, of the revoked certificate. * ```Revocation Date```: Date and time the certificate was revoked. * ```CRL Entry Extensions```: Optional extensions for the CRL entry. <li> ```X509v3 CRL Reason Code```: Reason the certificate was revoked. </li></li> * ```CRL Extensions```: Optional extensions for the CRL. <li> ```X509v3 Authority Key Identifier```: Identifies the public key associated with the private key used to sign the certificate. * ```X509v3 CRL Number:```: Decimal sequence number for the CRL. </li> * ```Signature Algorithm```: Algorithm used by your private CA to sign the CRL. * ```Signature Value```: Signature computed over the CRL. Certificate revocation lists created by ACM Private CA are DER-encoded. You can use the following OpenSSL command to list a CRL. <code>openssl crl -inform DER -text -in <i>crl_path</i> -noout</code> For more information, see
     * [[https://docs.aws.amazon.com/acm-pca/latest/userguide/crl-planning.html|Planning a certificate revocation list (CRL)]] in the <i>AWS Certificate Manager Private Certificate Authority (PCA) User Guide</i>
     */

aws-sdk-v2/services/appsync/src/main/scala/facade/amazonaws/services/AppSync.scala

@@ -237,9 +237,8 @@ package object appsync {
     }
   }
 
-  /** Describes an API key. Customers invoke AppSync GraphQL API operations with API keys as an identity mechanism. There are two key versions:
-    * ```da1```: We introduced this version at launch in November 2017. These keys always expire after 7 days. Amazon DynamoDB TTL manages key expiration. These keys ceased to be valid after February 21, 2018, and they should no longer be used. * <code>ListApiKeys</code> returns the expiration time in milliseconds. * <code>CreateApiKey</code> returns the expiration time in milliseconds. * <code>UpdateApiKey</code> is not available for this key version. * <code>DeleteApiKey</code> deletes the item from the table. * Expiration is stored in DynamoDB as milliseconds. This results in a bug where keys are not automatically deleted because DynamoDB expects the TTL to be stored in seconds. As a one-time action, we deleted these keys from the table on February 21, 2018.
-    * ```da2```: We introduced this version in February 2018 when AppSync added support to extend key expiration. * <code>ListApiKeys</code> returns the expiration time and deletion time in seconds. * <code>CreateApiKey</code> returns the expiration time and deletion time in seconds and accepts a user-provided expiration time in seconds. * <code>UpdateApiKey</code> returns the expiration time and and deletion time in seconds and accepts a user-provided expiration time in seconds. Expired API keys are kept for 60 days after the expiration time. You can update the key expiration time as long as the key isn't deleted. * <code>DeleteApiKey</code> deletes the item from the table. * Expiration is stored in DynamoDB as seconds. After the expiration time, using the key to authenticate will fail. However, you can reinstate the key before deletion. * Deletion is stored in DynamoDB as seconds. The key is deleted after deletion time.
+  /** Describes an API key. Customers invoke AppSync GraphQL API operations with API keys as an identity mechanism. There are two key versions: \```da1```: We introduced this version at launch in November 2017. These keys always expire after 7 days. Amazon DynamoDB TTL manages key expiration. These keys ceased to be valid after February 21, 2018, and they should no longer be used. * <code>ListApiKeys</code> returns the expiration time in milliseconds. * <code>CreateApiKey</code> returns the expiration time in milliseconds. * <code>UpdateApiKey</code> is not available for this key version. * <code>DeleteApiKey</code> deletes the item from the table. * Expiration is stored in DynamoDB as milliseconds. This results in a bug where keys are not automatically deleted because DynamoDB expects the TTL to be stored in seconds. As a one-time action, we deleted these keys from the table on February 21, 2018. \```da2```: We introduced this version in February 2018 when AppSync added support to
+    * extend key expiration. * <code>ListApiKeys</code> returns the expiration time and deletion time in seconds. * <code>CreateApiKey</code> returns the expiration time and deletion time in seconds and accepts a user-provided expiration time in seconds. * <code>UpdateApiKey</code> returns the expiration time and and deletion time in seconds and accepts a user-provided expiration time in seconds. Expired API keys are kept for 60 days after the expiration time. You can update the key expiration time as long as the key isn't deleted. * <code>DeleteApiKey</code> deletes the item from the table. * Expiration is stored in DynamoDB as seconds. After the expiration time, using the key to authenticate will fail. However, you can reinstate the key before deletion. * Deletion is stored in DynamoDB as seconds. The key is deleted after deletion time.
     */
   @js.native
   trait ApiKey extends js.Object {

aws-sdk-v2/services/cloudfront/src/main/scala/facade/amazonaws/services/CloudFront.scala

@@ -1877,9 +1877,8 @@ package object cloudfront {
     }
   }
 
-  /** This action deletes a web distribution. To delete a web distribution using the CloudFront API, perform the following steps.
-    * ```To delete a web distribution using the CloudFront API:``` <ol> * Disable the web distribution * Submit a <code>GET Distribution Config</code> request to get the current configuration and the <code>Etag</code> header for the distribution. * Update the XML document that was returned in the response to your <code>GET Distribution Config</code> request to change the value of <code>Enabled</code> to <code>false</code>. * Submit a <code>PUT Distribution Config</code> request to update the configuration for your distribution. In the request body, include the XML document that you updated in Step 3. Set the value of the HTTP <code>If-Match</code> header to the value of the <code>ETag</code> header that CloudFront returned when you submitted the <code>GET Distribution Config</code> request in Step 2. * Review the response to the <code>PUT Distribution Config</code> request to confirm that the distribution was successfully disabled. * Submit a <code>GET Distribution</code> request to
-    * confirm that your changes have propagated. When propagation is complete, the value of <code>Status</code> is <code>Deployed</code>. * Submit a <code>DELETE Distribution</code> request. Set the value of the HTTP <code>If-Match</code> header to the value of the <code>ETag</code> header that CloudFront returned when you submitted the <code>GET Distribution Config</code> request in Step 6. * Review the response to your <code>DELETE Distribution</code> request to confirm that the distribution was successfully deleted. </ol> For information about deleting a distribution using the CloudFront console, see [[https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/HowToDeleteDistribution.html|Deleting a Distribution]] in the <i>Amazon CloudFront Developer Guide</i>.
+  /** This action deletes a web distribution. To delete a web distribution using the CloudFront API, perform the following steps. 1 * \```To delete a web distribution using the CloudFront API:``` <ol> * Disable the web distribution * Submit a <code>GET Distribution Config</code> request to get the current configuration and the <code>Etag</code> header for the distribution. * Update the XML document that was returned in the response to your <code>GET Distribution Config</code> request to change the value of <code>Enabled</code> to <code>false</code>. * Submit a <code>PUT Distribution Config</code> request to update the configuration for your distribution. In the request body, include the XML document that you updated in Step 3. Set the value of the HTTP <code>If-Match</code> header to the value of the <code>ETag</code> header that CloudFront returned when you submitted the <code>GET Distribution Config</code> request in Step 2. * Review the response to the <code>PUT Distribution
+    * Config</code> request to confirm that the distribution was successfully disabled. * Submit a <code>GET Distribution</code> request to confirm that your changes have propagated. When propagation is complete, the value of <code>Status</code> is <code>Deployed</code>. * Submit a <code>DELETE Distribution</code> request. Set the value of the HTTP <code>If-Match</code> header to the value of the <code>ETag</code> header that CloudFront returned when you submitted the <code>GET Distribution Config</code> request in Step 6. * Review the response to your <code>DELETE Distribution</code> request to confirm that the distribution was successfully deleted. </ol> For information about deleting a distribution using the CloudFront console, see [[https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/HowToDeleteDistribution.html|Deleting a Distribution]] in the <i>Amazon CloudFront Developer Guide</i>.
     */
   @js.native
   trait DeleteDistributionRequest extends js.Object {