refactor[Logger]: replace console logging with logger service (#8271)

* refactor: replace console logging with logger service across multiple components

- Updated various files to utilize the logger service instead of console.log for improved logging consistency and error tracking.
- Enhanced logging levels to better categorize messages, including debug and error levels.
- Refactored logging in components such as ApiClientFactory, KnowledgeService, and MemoryProcessor to align with the new logging standards.

* refactor: update logging level in App component from error to info

- Changed the logging level in the App component to provide a more appropriate context for initialization messages, enhancing clarity in the logging output.

* refactor(logging): replace console.log with logger service in middleware and update ESLint comments

- Updated the logging implementation in the createSimpleLoggingMiddleware function to use logger.debug and logger.error instead of console.log and console.error for improved logging consistency.
- Added eslint-disable comments for restricted syntax in preload and useAppInit hooks to suppress warnings.

docs/technical/how-to-write-middlewares.md

@@ -80,7 +80,6 @@ import { ChunkType } from '@renderer/types' // 调整路径
 
 export const createSimpleLoggingMiddleware = (): CompletionsMiddleware => {
   return (api: MiddlewareAPI<AiProviderMiddlewareCompletionsContext, [CompletionsParams]>) => {
-    // console.log(`[LoggingMiddleware] Initialized for provider: ${api.getProviderId()}`);
 
     return (next: (context: AiProviderMiddlewareCompletionsContext, params: CompletionsParams) => Promise<any>) => {
       return async (context: AiProviderMiddlewareCompletionsContext, params: CompletionsParams): Promise<void> => {
@@ -88,7 +87,7 @@ export const createSimpleLoggingMiddleware = (): CompletionsMiddleware => {
         // 从 context 中获取 onChunk (它最初来自 params.onChunk)
         const onChunk = context.onChunk
 
-        console.log(
+        logger.debug(
           `[LoggingMiddleware] Request for ${context.methodName} with params:`,
           params.messages?.[params.messages.length - 1]?.content
         )
@@ -104,14 +103,14 @@ export const createSimpleLoggingMiddleware = (): CompletionsMiddleware => {
           // 如果在之前，那么它需要自己处理 rawSdkResponse 或确保下游会处理。
 
           const duration = Date.now() - startTime
-          console.log(`[LoggingMiddleware] Request for ${context.methodName} completed in ${duration}ms.`)
+          logger.debug(`[LoggingMiddleware] Request for ${context.methodName} completed in ${duration}ms.`)
 
           // 假设下游已经通过 onChunk 发送了所有数据。
           // 如果这个中间件是链的末端，并且需要确保 BLOCK_COMPLETE 被发送，
           // 它可能需要更复杂的逻辑来跟踪何时所有数据都已发送。
         } catch (error) {
           const duration = Date.now() - startTime
-          console.error(`[LoggingMiddleware] Request for ${context.methodName} failed after ${duration}ms:`, error)
+          logger.error(`[LoggingMiddleware] Request for ${context.methodName} failed after ${duration}ms:`, error)
 
           // 如果 onChunk 可用，可以尝试发送一个错误块
           if (onChunk) {
@@ -207,7 +206,7 @@ export default middlewareConfig
 
 ### 调试技巧
 
-- 在中间件的关键点使用 `console.log` 或调试器来检查 `params`、`context` 的状态以及 `next` 的返回值。
+- 在中间件的关键点使用 `logger.debug` 或调试器来检查 `params`、`context` 的状态以及 `next` 的返回值。
 - 暂时简化中间件链，只保留你正在调试的中间件和最简单的核心逻辑，以隔离问题。
 - 编写单元测试来独立验证每个中间件的行为。