GM2023 compatibility

• Added support for Script.staticVar (and a strict linter setting for constructors)
• Binary literals (0b101) are now supported.
• Added support for GMS2023 .resource_order file.
• Updated the included fnames to GM2023.1 and added type hints for some functions.

Other improvements

• ??= syntax sugar is no longer applied if the project is from GM2022 or newer.
• #RrGgBb literals now get a color tooltip too.
• Added @index_redirect JSDoc for macro tricks.
• Global search now forms a queue and works better with projects that contain incredible amounts (read: thousands) of searchable resources.

Fixes

• Fixed yet another case where indexer could error out given invalid code
• Fixed some constants not being detected
• Fixed #186 - type parameters inside function definitions may be mistaken for arguments.
  This change also improves function signature parsing in general.
• Fixed argument type hints un-collapsing for non-global functions with a space between name and (
• Fixed fields inside struct literals sometimes getting picked up as part of containing constructor/event
• Fixed freshly created note resources not always behaving like a note.
• Fixed some oddities with console warnings while loading APIs.
• Fixed #189 - new ctr().func() lints as new (ctr().func()) rather than (new ctr()).func()
• Fixed some issues with API parser not accepting syntax that is otherwise allowed in GMEdit.
• Fixed #191 - linter shows warnings for object properties (which aren’t real code)