Refactor API endpoints to use '/api/lm/' prefix

- Updated all relevant routes in `stats_routes.py` and `update_routes.py` to include the new '/api/lm/' prefix for consistency.
- Modified API endpoint configurations in `apiConfig.js` to reflect the new structure, ensuring all CRUD and bulk operations are correctly routed.
- Adjusted fetch calls in various components and managers to utilize the updated API paths, including recipe, model, and example image operations.
- Ensured all instances of the old API paths were replaced with the new '/api/lm/' prefix across the codebase for uniformity and to prevent broken links.

static/js/managers/import/FolderBrowser.js

@@ -100,7 +100,7 @@ export class FolderBrowser {
             }
             
             // Fetch LoRA roots
-            const rootsResponse = await fetch('/api/loras/roots');
+            const rootsResponse = await fetch('/api/lm/loras/roots');
             if (!rootsResponse.ok) {
                 throw new Error(`Failed to fetch LoRA roots: ${rootsResponse.status}`);
             }
@@ -120,7 +120,7 @@ export class FolderBrowser {
             }
             
             // Fetch folders
-            const foldersResponse = await fetch('/api/loras/folders');
+            const foldersResponse = await fetch('/api/lm/loras/folders');
             if (!foldersResponse.ok) {
                 throw new Error(`Failed to fetch folders: ${foldersResponse.status}`);
             }