mw/com: migrate_umlet_to_plantuml__shared_mem_layout

Closes eclipse-score#49

Issue: SWP-208704
GIT_ORIGIN_SPP_REV_ID: d7836e315f6c4a87c04c75613c0a0cbfc73983a8

Author: Abhishek2581

score/mw/com/design/shared_mem_layout/README.md

@@ -7,7 +7,7 @@ within shared-memory by `Lola`. Other parts of the design documentation e.g.
 [event and field description part](../events_fields/README.md#introduction) already describe/hint in their class
 diagrams via the stereotype `<<SharedMemory>>` in the following form:
 
-![Stereotype](artifacts/stereotype.svg)
+![Stereotype](stereotype.svg)
 
 whether some classes (instances of it) are partially placed within shared-memory. We use the same stereotype here, but
 give a complete overview.
@@ -36,13 +36,13 @@ The following class diagram provides an overview of the classes, whose instances
 also a rough indication how the provider side (in the form of `LoLa` skeleton) and the consumer side (in the form of
 `LoLa` proxy/proxy-event) interact with them.
 
-![Class View](broken_link_k/swh/ddad_score/mw/com/design/shared_mem_layout/artifacts/shared_mem_layout_classdiagram.uxf?ref=18c835c8d7b01056dd48f257c14f435795a48b7d)
+![SHARED_MEM_LAYOUT_CLASSDIAGRAM](broken_link_k/swh/safe-posix-platform/score/mw/com/design/shared_mem_layout/shared_mem_layout_classdiagram.puml")
 
 This object diagram below (showing a concrete instantiation of the class diagram above for some example service instance)
 depicts more clearly the relation between the `SharedMemoryResource` instances representing a shared-memory object and the
 anchor/root elements placed within shared-memory:
 
-![Object View](broken_link_k/swh/ddad_score/mw/com/design/shared_mem_layout/artifacts/shared_mem_layout_objectdiagram.uxf?ref=18c835c8d7b01056dd48f257c14f435795a48b7d)
+![SHARED_MEM_LAYOUT_OBJECTDIAGRAM](broken_link_k/swh/safe-posix-platform/score/mw/com/design/shared_mem_layout/shared_mem_layout_objectdiagram.puml")
 
 So - the first object/element created within the shared-memory object for **Data** (represented by `SharedMemoryResource`
 instance `shmResource_storage_SI_1`) is the instance `serviceDataStorage_SI_1` of class `ServiceDataStorage` and
@@ -70,8 +70,8 @@ This anchor element of the `SharedMemoryResource` contains two members:
   ```
   are stored here as "type-erased" `score::memory::shared::OffsetPtr<void>`, because every slot-vector has a different
   type and only later when the skeleton events register themselves dynamically or access that storage they are cast to
-  the effective/concrete type. 
-  
+  the effective/concrete type.
+
 * `events_metainfo_`: a map for meta information of every event the service provides
 * `skeleton_pid_`: PID of the provider/skeleton process.
 
@@ -83,4 +83,3 @@ created by a `LoLa` skeleton instance during `lola::Skeleton::PrepareOffer()` wi
 callback of the newly created shared-memory object.
 This anchor element of the `SharedMemoryResource` contains the member:
 * `event_data_control_`: a map containing the control slots of every event the service provides.
-