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/UpdateService.js

@@ -97,7 +97,7 @@ export class UpdateService {
         
         try {
             // Call backend API to check for updates with nightly flag
-            const response = await fetch(`/api/check-updates?nightly=${this.nightlyMode}`);
+            const response = await fetch(`/api/lm/check-updates?nightly=${this.nightlyMode}`);
             const data = await response.json();
             
             if (data.success) {
@@ -280,7 +280,7 @@ export class UpdateService {
             // Update progress
             this.updateProgress(10, translate('update.updateProgress.preparing'));
             
-            const response = await fetch('/api/perform-update', {
+            const response = await fetch('/api/lm/perform-update', {
                 method: 'POST',
                 headers: {
                     'Content-Type': 'application/json'
@@ -444,7 +444,7 @@ export class UpdateService {
     async checkVersionInfo() {
         try {
             // Call API to get current version info
-            const response = await fetch('/api/version-info');
+            const response = await fetch('/api/lm/version-info');
             const data = await response.json();
             
             if (data.success) {