update documentation links

Signed-off-by: Stanchev Aleksandar <aleksandar.stanchev@bosch.com>

documentation/src/main/resources/architecture/DADR-0003-do-not-interrupt-threads.md

@@ -28,5 +28,5 @@ Use `CompletableFuture.join()` instead of `CompletableFuture.get()` in tests.
 
 Where blocking-wait cannot be avoided, the actors executing blocking wait should execute in their own dispatcher
 to not starve the actor system of threads. Use
-[PinnedDispatcher](https://doc.akka.io/docs/akka/current/dispatchers.html)
+[PinnedDispatcher](https://pekko.apache.org/docs/pekko/current/dispatchers.html)
 for example to give each blocking actor its own thread.

documentation/src/main/resources/openapi/ditto-api-2.yml

@@ -7403,7 +7403,7 @@ paths:
             example: |-
               {
                 "level": "info",
-                "logger": "akka.actor.CoordinatedShutdown"
+                "logger": "org.apache.pekko.actor.CoordinatedShutdown"
               }
       responses:
         '201':
@@ -7459,7 +7459,7 @@ paths:
             example: |-
               {
                 "level": "info",
-                "logger": "akka.actor.CoordinatedShutdown"
+                "logger": "org.apache.pekko.actor.CoordinatedShutdown"
               }
       responses:
         '201':

documentation/src/main/resources/openapi/sources/paths/logging/logging.yml

@@ -51,7 +51,7 @@ put:
         example: |-
           {
             "level": "info",
-            "logger": "akka.actor.CoordinatedShutdown"
+            "logger": "org.apache.pekko.actor.CoordinatedShutdown"
           }
   responses:
     '201':

documentation/src/main/resources/openapi/sources/paths/logging/moduleName.yml

@@ -55,7 +55,7 @@ put:
         example: |-
           {
             "level": "info",
-            "logger": "akka.actor.CoordinatedShutdown"
+            "logger": "org.apache.pekko.actor.CoordinatedShutdown"
           }
   responses:
     '201':

documentation/src/main/resources/pages/ditto/architecture-overview.md

@@ -27,7 +27,7 @@ The components have the following tasks:
    * persistence of [Connections](basic-connections.html)
    * sends [Ditto Protocol](protocol-overview.html) messages to external message brokers and receives messages from them
 
-All services run in the same [Akka cluster](https://doc.akka.io/docs/akka/current/typed/cluster-concepts.html) and can
+All services run in the same [Pekko cluster](https://pekko.apache.org/docs/pekko/current/typed/cluster-concepts.html) and can
 reach each other via TCP without the need for an additional message broker in between.
 
 ## Components
@@ -43,7 +43,7 @@ A "microservice" in Ditto is defined as:
 ## Communication
 
 All microservices can communicate asynchronously in a Ditto cluster. Communication is done via 
-[Akka remoting](https://doc.akka.io/docs/akka/current/general/remoting.html) which means that each service acts as server, 
+[Pekko remoting](https://pekko.apache.org/docs/pekko/current/general/remoting.html) which means that each service acts as server, 
 providing a TCP endpoint, as well as client sending data to other services.
 
 All messages which are sent between Ditto microservices must in a way be serializable and deserializable.  

documentation/src/main/resources/pages/ditto/architecture-services-connectivity.md

@@ -31,7 +31,7 @@ Other services can communicate with the connectivity service via:
 
 ## Persistence
 
-The connectivity service uses [Akka persistence](https://doc.akka.io/docs/akka/current/persistence.html?language=java) and 
+The connectivity service uses [Pekko persistence](https://pekko.apache.org/docs/pekko/current/persistence.html?language=java) and 
 with that [Event sourcing](basic-signals.html#architectural-style) in order to persist changes to 
 and restore persisted [connections](basic-connections.html).
 

documentation/src/main/resources/pages/ditto/architecture-services-policies.md

@@ -25,7 +25,7 @@ Other services can communicate with the policies service via:
 
 ## Persistence
 
-The policies service uses [Akka persistence](https://doc.akka.io/docs/akka/current/persistence.html?language=java) and 
+The policies service uses [Pekko persistence](https://pekko.apache.org/docs/pekko/current/persistence.html?language=java) and 
 with that [Event sourcing](basic-signals.html#architectural-style) in order to persist changes to  
 and restore persisted [policies](basic-policy.html).
 

documentation/src/main/resources/pages/ditto/architecture-services-things.md

@@ -24,7 +24,7 @@ Other services can communicate with the things service via:
 
 ## Persistence
 
-The things service uses [Akka persistence](https://doc.akka.io/docs/akka/current/persistence.html?language=java) and 
+The things service uses [Pekko persistence](https://pekko.apache.org/docs/pekko/current/persistence.html?language=java) and 
 with that [Event sourcing](basic-signals.html#architectural-style) in order to persist changes to 
 and restore persisted [things](basic-thing.html).
 

documentation/src/main/resources/pages/ditto/client-sdk-java.md

@@ -222,7 +222,7 @@ Publisher<List<Thing>> publisher = client.twin().search()
       .options(builder -> builder.sort(s -> s.desc("thingId")).size(1))
    );
 // integrate the publisher in the reactive streams library of your choice, e.g. Akka streams:
-akka.stream.javadsl.Source<Thing, NotUsed> things = akka.stream.javadsl.Source.fromPublisher(publisher)
+org.apache.pekko.stream.javadsl.Source<Thing, NotUsed> things = org.apache.pekko.stream.javadsl.Source.fromPublisher(publisher)
    .flatMapConcat(Source::from);
 // .. proceed working with the Akka Source ..
 ```

documentation/src/main/resources/pages/ditto/installation-operating.md

@@ -5,7 +5,7 @@ keywords: operating, docker, docker-compose, devops, logging, logstash, elk, mon
 permalink: installation-operating.html
 ---
 
-[pubsubmediator]: https://doc.akka.io/docs/akka/current/distributed-pub-sub.html
+[pubsubmediator]: https://pekko.apache.org/docs/pekko/current/distributed-pub-sub.html
 
 Once you have successfully started Ditto, proceed with setting it up for continuous operation.