Please address the comments from this code review:
## Overall Comments
- Avoid mutating axios.defaults.adapter globally; instead, apply the consoleFetch adapter on a dedicated axios instance to prevent unintended side effects for other modules.
- In consoleFetchAxiosAdapter, consider parsing JSON responses automatically based on Content-Type so non-GraphQL REST endpoints return structured objects instead of raw strings.
- In webpack resolve.extensions, it’s more conventional (and safer) to list .ts/.tsx before .js/.jsx so TypeScript sources are resolved before their JavaScript counterparts.

## Individual Comments

### Comment 1
<location> `ui/apps/platform/src/ConsolePlugin/consoleFetchAxiosAdapter.ts:44` </location>
<code_context>
+            };
+        })
+        .catch((error) => {
+            throw new AxiosError(error.message);
+        });
+}
</code_context>

<issue_to_address>
AxiosError instantiation may lose important error context.

Passing only error.message discards valuable information like the stack trace. Pass the original error or include additional context to preserve debugging details.
</issue_to_address>

<suggested_fix>
<<<<<<< SEARCH
        .catch((error) => {
+            throw new AxiosError(error.message);
=======
        .catch((error) => {
+            // Preserve original error context by passing the original error object and stack trace
+            const axiosError = new AxiosError(
+                error.message,
+                undefined,
+                config,
+                undefined,
+                error.response
+            );
+            axiosError.stack = error.stack;
+            // Attach the original error for further debugging if needed
+            (axiosError as any).originalError = error;
+            throw axiosError;
>>>>>>> REPLACE

</suggested_fix>

### Comment 2
<location> `ui/apps/platform/src/ConsolePlugin/consoleFetchAxiosAdapter.ts:27` </location>
<code_context>
+            // GraphQL request errors are JSON objects with an `errors` field an a HTTP status code of 200, so we
+            // need to check for that and throw an ApolloError
+            if (config.url?.startsWith('/api/graphql')) {
+                const json = JSON.parse(data);
+                if ('errors' in json) {
+                    throw new ApolloError({ graphQLErrors: json.errors });
</code_context>

<issue_to_address>
Potential unhandled exception if response is not valid JSON.

Wrap JSON.parse in a try/catch block or check the response content type before parsing to prevent unhandled exceptions.
</issue_to_address>