GDScript: Fix lambda resolution with cyclic references

[dalexeev]

• Closes Cannot access member variable from lambda body due cyclic reference #70592.
• This PR allows lambda body to use class members in any order (but you still have to consider the order in which initializer expressions are evaluated if they call lambdas).
• The lambda signature is still respected in member resolution (because argument initializers don't have to be literals).
• call() arguments should also not create cyclic references, as they are part of the outer expression, not part of lambda body.

[adamscott]

Everything seems in order!

[YuriSizov]

Thanks!

[rune-scape]

im curious if the lambda body resolution could be delayed until the very end of the current scope, (class, function, script) without any issues

[dalexeev]

Lambda body resolution is delayed until the end of the member variable definition (otherwise you cannot call the lambda recursively) and until the end of the statement in the case of local expressions, not until the end of the class/function. No problems found so far, let me know if you find one.