Fixes linter failing by disabling @ts/await-thenable rule for mixed sync/async patterns

Turns off the problematic await-thenable ESLint rule to accommodate
common usage of Promise aggregation with mixed synchronous and
asynchronous values, preventing unnecessary code complexity.
Also removes outdated inline disables for to-string lint warnings.

(#4638, #4639)

Author: sergeibbb

eslint.config.mjs

@@ -282,6 +282,11 @@ export default ts.config(
 			],
 
 			// TypeScript rules
+
+			// @typescript-eslint/await-thenable is disabled because Promise.allSettled/all with mixed thenable/non-thenable arrays
+			// is a valid pattern used throughout the codebase for handling mixed sync/async operations safely.
+			// The new stricter rule would require unnecessary complexity to separate sync/async values before Promise aggregation.
+			'@typescript-eslint/await-thenable': 'off',
 			'@typescript-eslint/consistent-type-assertions': [
 				'error',
 				{ assertionStyle: 'as', objectLiteralTypeAssertions: 'allow-as-parameter' },

src/plus/ai/aiProviderService.ts

@@ -1708,7 +1708,6 @@ export class AIProviderService implements Disposable {
 				setLogScopeExit(
 					scope,
 					`model: ${model.provider.id}/${model.id}`,
-					// eslint-disable-next-line @typescript-eslint/no-base-to-string
 					`failed: ${String(ex)} (${String(ex.original)})`,
 				);
 
@@ -1718,7 +1717,6 @@ export class AIProviderService implements Disposable {
 						...telementry.data,
 						duration: Date.now() - start,
 						failed: true,
-						// eslint-disable-next-line @typescript-eslint/no-base-to-string
 						'failed.error': String(ex),
 						'failed.error.detail': String(ex.original),
 					},