Describe the bug

It is now (after #8635) impossible to invoke a Nu script with an argument which is a string starting with a number.

Essentially same as #8788 but that issue was falsely closed.

How to reproduce

> cat foo.nu
#!/usr/bin/env nu
def main [s: string] {
  echo $s
}
> chmod +x foo.nu
> let s = '1bar'
> ./foo.nu $s        # gives the same error as below, omitted
> ./foo.nu $'"($s)"' # awful but expected to work, yet the error remains
Error: nu::parser::type_mismatch

  × Type mismatch during operation.
   ╭─[<commandline>:1:1]
 1 │ main 1bar
   ·      ───┬──
   ·         ╰── expected string, found number-like value (hint: use quotes or backticks)
   ╰────

Expected behavior

I expect at least the foo $'"($s)"' approach to work. Or even better we have #8635 reverted...

Making such functions a module should work, but not so optimal for invoking inside another script or module.

Screenshots

No response

Configuration

Additional context

By the way this could have mingled with #7936, because foo $"''($str)''" prints 1bar, not '1bar'.