Correct docs for AWS support

* The `DynamoDbLockRegistry` is now a part of Spring Cloud AWS project
* The `DynamoDbMetadataStore` is now a part of Spring Cloud AWS project

Author: artembilan

src/reference/antora/modules/ROOT/pages/distributed-locks.adoc

@@ -33,7 +33,7 @@ Spring Integration provides these `LockRegistry` implementations for distributed
 * xref:redis.adoc#redis-lock-registry[Redis]
 * xref:zookeeper.adoc#zk-lock-registry[Zookeeper]
 
-https://github.com/spring-projects/spring-integration-aws[Spring Integration AWS] extension also implements a `DynamoDbLockRegistry`.
+The https://awspring.io[Spring Cloud AWS] also provides a `DynamoDbLockRegistry`.
 
 Starting with version 7.0, the `DistributedLock` interface has been introduced, providing new methods, `lock(Duration ttl`) and `tryLock(long time, TimeUnit unit, Duration ttl)`, to acquire a lock with a custom time-to-live (TTL).
 Both `JdbcLock` and `RedisLock` implement `DistributedLock` interface to support the feature of customized time-to-live.

src/reference/antora/modules/ROOT/pages/meta-data-store.adoc

@@ -20,6 +20,8 @@ If you need to persist metadata between application context restarts, the framew
 * xref:redis.adoc#redis-metadata-store[Redis Metadata Store]
 * xref:zookeeper.adoc#zk-metadata-store[Zookeeper Metadata Store]
 
+The https://awspring.io[Spring Cloud AWS] also provides a `DynamoDbMetadataStore`.
+
 The `PropertiesPersistingMetadataStore` is backed by a properties file and a https://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/util/PropertiesPersister.html[`PropertiesPersister`].
 
 By default, it persists only in the state when the application context is closed normally.