- Honor the OPTION_ROBOT_TIMEOUT_USE for initialization as well

[lmartorella]

Hello,
I've found that even setting the VSCode setting robot.timeout.use to false, the language server fails to start with the following stack, in loop:

Traceback (most recent call last):
  File "<home>\.vscode\extensions\robocorp.robotframework-lsp-1.10.2\src\robotframework_ls\server_manager.py", line 330, in get_robotframework_api_client
    api.initialize(
  File "<home>\.vscode\extensions\robocorp.robotframework-lsp-1.10.2\src\robotframework_ls\server_api\client.py", line 63, in initialize
    return self.request(
           ^^^^^^^^^^^^^
  File "<home>\.vscode\extensions\robocorp.robotframework-lsp-1.10.2\src\robotframework_ls\vendored\robocorp_ls_core\client_base.py", line 381, in request
    raise TimeoutError("Request timed-out (%s): %s" % (timeout, contents))
TimeoutError: Request timed-out (30): {'jsonrpc': '2.0', 'id': 0, 'method': 'initialize', 'params': {'processId': 29228, 'rootUri': 'file:///c%3A/dev/my-project', 'workspaceFolders': [{'uri': 'file:///c%3A/dev/my-project', 'name': 'my-project'}]}}
lsp: 2023-05-17 16:42:59 UTC pid: 29228 - MainThread - INFO - robotframework_ls.robotframework_ls_impl

Not sure if this is due to high count of test in my project. By the way, applying the following fix it makes the RF language to start seamlessly.
Thanks, L

[CLAassistant]

All committers have signed the CLA.