Use standard format when write to "Rust Analyzer Client" log

Current output in "Rust Analyzer Client" looks like:

INFO [18.02.2023, 16:20:11]: Using server binary at c:\Users\Mingun\.vscode\extensions\rust-lang.rust-analyzer-0.4.1407-win32-x64\server\rust-analyzer.exe
INFO [18.02.2023, 16:20:11]: c:\Users\Mingun\.vscode\extensions\rust-lang.rust-analyzer-0.4.1407-win32-x64\server\rust-analyzer.exe --version: {
  status: 0,
  signal: null,
  output: [
    null,
    'rust-analyzer 0.4.1407-standalone (a6603fc21 2023-02-16)\n',
    ''
  ],
  pid: 14900,
  stdout: 'rust-analyzer 0.4.1407-standalone (a6603fc21 2023-02-16)\n',
  stderr: ''
}

I think, that due to level/timestamp format it is not recognized by the МЫ Code log highlighter. Compare with output of "Window" log (name is approximate, in my Russian localization it is "Окно") for example:

2023-02-18 16:19:58.681 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'github.vscode-pull-request-github' wants API proposal 'commentsResolvedState' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2023-02-18 16:20:05.983 [warning] [redhat.vscode-yaml]: Невозможно зарегистрировать "redhat.telemetry.enabled". Это свойство уже зарегистрировано.
2023-02-18 16:20:10.788 [error] [Extension Host] (node:5628) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `Code --trace-deprecation ...` to show where the warning was created)
2023-02-18 16:20:11.063 [info] [perf] Render performance baseline is 91ms
2023-02-18 16:20:53.469 [info] The pty host became responsive again
2023-02-18 16:21:16.935 [info] UNRESPONSIVE extension host: starting to profile NOW
2023-02-18 16:21:16.997 [info] UNRESPONSIVE extension host: received responsive event and cancelling profiling session
2023-02-18 16:21:25.385 [info] UNRESPONSIVE extension host: starting to profile NOW
2023-02-18 16:21:27.472 [info] UNRESPONSIVE extension host: received responsive event and cancelling profiling session

Start by locating the code that produces the "Rust Analyzer Client" log output and compare its level and timestamp format with the Window log example in the issue. Done means the client log uses the standard format and is recognized by the VS Code log highlighter.