When robot LSP initialises Libraries for Libdoc generation, it passes in variable names instead of values

[Serhiy1]

Describe the bug
When robot LSP initialises a Library with arguments, it passes in the variable names as arguments instead of their values

To Reproduce

Example library

from robot.api.deco import library

@library(scope="SUITE", auto_keywords=True)
class example:

    def __init__(self, arg_1: str, arg_2: str, arg_3: str):
        raise ValueError(f"arg_1 {arg_1}, arg_2 {arg_2}, arg_2 {arg_2}")

Example usage

*** Settings ***
Library    example.py    ${ARG_1}    ${ARG_2}    ${ARG_3}


*** Variables ***
${ARG_1}=    foo
${ARG_2}=    bar
${ARG_3}=    baz

Error message showing that the variable names get passed in

Unresolved library: example.py.
Error generating libspec:
Initializing library 'example' with arguments [ ${ARG_1} | ${ARG_2} | ${ARG_3} ] failed: ValueError: arg_1 ${ARG_1}, arg_2 ${ARG_2} arg_2 ${ARG_2},

Error message when the variables in the robot file are replaced with string literals

Unresolved library: example.py.
Error generating libspec:
Initializing library 'example' with arguments [ foo | bar | baz ] failed: ValueError: arg_1 foo, arg_2 bar, arg_2 bar

Expected behavior
LSP should pass in the Values of the variables instead of the names

[fabioz]

This should be fixed in the 0.43.5 pre-release (please test it -- if everything is ok a new stable release should be done -- hopefully tomorrow).

[Serhiy1]

@fabioz I can verify that the Libraries that got variables as arguments are now working correctly for me in the pre-release