refactor(frontend): organize import statements in fitness routes

- Reorder import statements in fitness route components
- Improve import organization for better readability
- Remove unnecessary import order variations

Author: IgnisDa

apps/frontend/app/routes/_dashboard.fitness.$action.tsx

@@ -149,11 +149,11 @@ import {
 	useGetSetAtIndex,
 	useMeasurementsDrawerOpen,
 } from "~/lib/state/fitness";
-import type { Route } from "./+types/_dashboard.fitness.$action";
 import {
 	OnboardingTourStepTargets,
 	useOnboardingTour,
 } from "~/lib/state/general";
+import type { Route } from "./+types/_dashboard.fitness.$action";
 
 const DEFAULT_SET_TIMEOUT_DELAY = 800;
 

apps/frontend/app/routes/_dashboard.fitness.exercises.list.tsx

@@ -84,6 +84,11 @@ import {
 	useCurrentWorkout,
 	useMergingExercise,
 } from "~/lib/state/fitness";
+import {
+	OnboardingTourStepTargets,
+	TOUR_EXERCISE_TARGET_ID,
+	useOnboardingTour,
+} from "~/lib/state/general";
 import {
 	getEnhancedCookieName,
 	redirectToFirstPageIfOnInvalidPage,
@@ -92,11 +97,6 @@ import {
 	serverGqlService,
 } from "~/lib/utilities.server";
 import type { Route } from "./+types/_dashboard.fitness.exercises.list";
-import {
-	OnboardingTourStepTargets,
-	TOUR_EXERCISE_TARGET_ID,
-	useOnboardingTour,
-} from "~/lib/state/general";
 
 const defaultFiltersValue = {
 	muscle: undefined,