Luau type fixes for luau-lsp

[tapple]

Part of a set of PR's improving the definitions and keywords files in lsl and slua:

• Add slua_definitions.yaml lsl-definitions#38
• Type-fixes viewer#5288
  • Updates and improvements to keywords_lua_default.xml viewer#5301
• Luau type fixes for luau-lsp #57
• Make the xml output better match files in the sim/viewer python-llsd#37

---

I significantly improved the luau types of most functions, so that luau-lsp gives less errors

• Fixes Type-check fails on valid statement (Vector multiplied by Number) #56

Here's the diff for the generated slua-default.d.luau:

• Before: slua_before.d.luau.txt
• After: slua_default.d.luau.txt
• Diff: slua_default.d.luau.diff.txt

I added several fields to the definition file:

• luaType: for when lua has a different or more-specific typing than lsl
• luaReturn: same thing, but for return values
• typeParameters: function generic<TYPE, PARAMETERS>()

I'm aware the plugin isn't the master source of lua typings. I can convert this PR to xml and submit a new PR in one of or more of these places, if desired:

• https://github.com/secondlife/lsl-definitions/blob/main/lsl_definitions.yaml
• https://github.com/secondlife/viewer/blob/project/lua_editor/indra/newview/app_settings/keywords_lua_default.xml
• https://github.com/secondlife/viewer/blob/project/lua_editor/indra/newview/app_settings/types_lua_default.xml

[tapple]

I tried merging this and #51 into the same branch, and there are only 3 trivial merge conflicts. I recommend merging #51 before this PR

[marchcat]

Pre-commit fails due to trailing whitespaces in src/shared/luadefsgenerator.ts and EOF in data/syntax_def_default.json.

[WolfGangS]

The trailing whitespace is fixed in #50. It's a problem in the repo itself not this pr.

[Rider-Linden]

There are a couple places where the luaType is set to numberic but I think it should be boolean...

[Rider-Linden]

Shouldn't this be boolean?

[WolfGangS]

All lsl functions exposed through ll.* that accept integer in lsl, accept boolean|number in slua.

For instance

ll.SetColor(vector(1,0,0),true)

The choice could be made to say we want to mark it as a boolean, but that would cause either

• linters to choke on code that saves and runs perfectly fine
• linter definition generation to do extra interpreting to figure out if it accepts something other than boolean

[Rider-Linden]

I confused number with numeric didn't I...