task(devx): Added light/dark image switcher and dark themed svgs

docs/content/about-iota/iota-architecture/iota-architecture.mdx

@@ -1,6 +1,7 @@
 ---
 title: IOTA Architecture
 ---
+import ThemedImage from '@theme/ThemedImage';
 
 IOTA shares some similarities with other blockchains but is unique in many ways. Use the topics in this section to understand the features that define the IOTA network.
 
@@ -39,4 +40,10 @@ The core components are:
 - [IOTA RPC](../../references/iota-api)
 - [IOTA CLI](../../references/cli)
 
-![IOTA Architecture](/img/concepts/execution-architecture/iota-architecture.svg)
+<ThemedImage
+    alt='IOTA Architecture'
+    sources={{
+    light: '/img/concepts/execution-architecture/iota-architecture.svg',
+    dark: '/img/concepts/execution-architecture/dark/iota-architecture.svg',
+    }}
+/>

docs/content/developer/stardust/migration-process.mdx

@@ -3,6 +3,7 @@ title: Migration Process
 description: Explains how IOTA assets are handled during migration
 ---
 import MigrationWarning from '../../_snippets/migration-warning.mdx';
+import ThemedImage from '@theme/ThemedImage';
 
 <MigrationWarning/ >
 
@@ -116,7 +117,13 @@ which they can be identified as vesting reward objects.
 
 The full decision graph (without the vesting reward output case) is depicted here (with `coin` being `IOTA`):
 
-![Stardust on Move Migration Graph](/img/guides/developer/advanced/stardust-on-move/stardust-on-move-migration-graph.svg)
+<ThemedImage
+alt='Stardust on Move Migration Graph'
+sources={{
+light: '/img/guides/developer/advanced/stardust-on-move/stardust-on-move-migration-graph.svg',
+dark: '/img/guides/developer/advanced/stardust-on-move/dark/stardust-on-move-migration-graph.svg',
+}}
+/>
 
 ## Alias Outputs
 

docs/content/references/execution-architecture/adapter.mdx

@@ -2,6 +2,7 @@
 title: Adapter
 description: This document describes the architectural approach and execution flow for the adapter and related components.
 ---
+import ThemedImage from '@theme/ThemedImage';
 
 ## Move Adapter
 
@@ -78,4 +79,12 @@ Also used as a cache that is used after the execution to populate the created/mo
 
 ### Flow 
 
-![IOTA Adapter Flow](/img/concepts/execution-architecture/iota-adapter.svg)
+
+<ThemedImage
+alt='IOTA Adapter Flow'
+    sources={{
+    light: '/img/concepts/execution-architecture/iota-adapter.svg',
+    dark: '/img/concepts/execution-architecture/dark/iota-adapter.svg',
+    }}
+/>
+

docs/content/references/execution-architecture/iota-execution.mdx

@@ -3,10 +3,18 @@ title: IOTA Execution Crate
 description: This document describes the architectural approach for iota execution crate.
 ---
 
-## IOTA Execution Architecture
+import ThemedImage from '@theme/ThemedImage';
+
+# IOTA Execution Architecture
 
 The IOTA Execution Architecture, depicted in the included architectural diagram, outlines the technical approach for the iota execution crate to have a general view of component interaction. 
 The following diagram is a visual representation of the iota_execution crate with its subcrates ([iota_adapter](adapter.mdx), [iota_move_natives](natives.mdx), iota_verifier).
 The main purposes of iota execution are executing transactions (including PTBs), gas accounting, and supporting native functions.
 
-![IOTA Execution Architecture](/img/concepts/execution-architecture/iota-execution.svg)
+<ThemedImage
+    alt='IOTA Execution Architecture'
+    sources={{
+    light: '/img/concepts/execution-architecture/iota-execution.svg',
+    dark: '/img/concepts/execution-architecture/dark/iota-execution.svg',
+    }}
+/>

docs/content/references/execution-architecture/natives.mdx

@@ -2,6 +2,7 @@
 title: Natives & Object Runtime
 description: This document describes the object runtime and native functions flow.
 ---
+import ThemedImage from '@theme/ThemedImage';
 
 ## IOTA Move Natives
 
@@ -16,7 +17,14 @@ pub fn all_natives(silent: bool) -> NativeFunctionTable
 Contains all registered native functions.
 The resulting NativeFunctionTable object contains information about all the native functions that can be called from a Move contract.
 
-![Native functions](/img/concepts/execution-architecture/native-fns-flow.svg)
+<ThemedImage
+    alt='Native functions'
+    sources={{
+    light: '/img/concepts/execution-architecture/native-fns-flow.svg',
+    dark: '/img/concepts/execution-architecture/dark/native-fns-flow.svg',
+}}
+/>
+
 
 ## Object runtime
 
@@ -29,4 +37,4 @@ It serves as the core interface for interacting, transferring the objects, manag
 - Child object management etc
 Also handles information about transaction objects, which are stored in the ObjectRuntimeState as an internal state.
 
-Object store - manages child/dynamic objects(inner store).
+Object store - manages child/dynamic objects(inner store).