text: Title: Problems with recommentation to use `$var` syntax if expression evaluation fails
  Body: A common error when evaluating expressions with IF or otherwise is using something like
  ```
  IF    ${x} == 'expected'
      Keyword
  END
  ```
  The resulting error message was enhanced in RF 6.1 (#4676) to recommend using the `$x` syntax, and what you get nowadays is something like this:
  > Invalid IF condition: Evaluating expression "xxx == 'expected'" failed: NameError: name 'xxx' is not defined nor importable as module
  >
  > Variables in the original expression "${x} == 'expected'" were resolved before the expression was evaluated. Try using "$x == 'expected'" syntax to avoid that. See Evaluating Expressions appendix in Robot Framework User Guide for more details.
  
  This works fine otherwise, but if the variable has been quoted and evaluation fails because the variable contains a matching quote or a newline. For example, if `${x}` contains `x'x` and you use
  ```
  IF    '${x}' == 'expected'
      Keyword
  END
  ```
  the recommendation part of the error is this:
  > Try using "'$x' == 'expected'" syntax to avoid that.
  
  The above recommendation isn't correct, because `'$x'` would be treated as a literal string where `$x` has no special meaning. The correct recommendation would be this one without quotes around `$x`:
  > Try using "$x == 'expected'" syntax to avoid that.
  
  Although this is only a recommendation in an error situation, the recommendation being wrong is somewhat severe. Luckily it is pretty easy to detect is the original variable quoted and remove quotes in that case.