Refactor simulation paths to simulation states

- Updated all instances of `simulationPaths` to `simulationStates` across multiple components including copyPasteControls, duplicationControls, moveControls, rotateControls, selectionControls, and others.
- Adjusted related state management hooks in the store to reflect the change from `simulationPaths` to `simulationStates`.
- Ensured that all references to simulation paths in the simulation logic and UI components are consistent with the new naming convention.

app/src/modules/simulation/simulation.tsx

@@ -2,7 +2,7 @@ import { useState, useEffect, useRef, useMemo } from "react";
 import {
   useSelectedActionSphere,
   useSelectedPath,
-  useSimulationPaths,
+  useSimulationStates,
 } from "../../store/store";
 import * as THREE from "three";
 import Behaviour from "./behaviour/behaviour";
@@ -15,12 +15,12 @@ import Agv from "../builder/agv/agv";
 function Simulation() {
   const { activeModule } = useModuleStore();
   const pathsGroupRef = useRef() as React.MutableRefObject<THREE.Group>;
-  const { simulationPaths, setSimulationPaths } = useSimulationPaths();
+  const { simulationStates, setSimulationStates } = useSimulationStates();
   const [processes, setProcesses] = useState([]);
 
   useEffect(() => {
-    // console.log('simulationPaths: ', simulationPaths);
-  }, [simulationPaths]);
+    // console.log('simulationStates: ', simulationStates);
+  }, [simulationStates]);
 
   // useEffect(() => {
   //     if (selectedActionSphere) {