v0.0.5-rc.2 - use `@self` in `.typedefs` and new `init.luau` semantics by default

Looks like luau-lsp updated to the new init.luau require-by-string semantics without a backwards-compatibility option, breaking our type definitions with the newest luau-lsp. seal wants to be current with luau and luau-lsp so we're updating to @self type definitions without a compatibility option for now. Note that seal still supports the old resolution semantics at runtime but it won't be the default anymore either

v0.0.5-rc.1 - requires fixed!

Features

• env.cwd() replaces env.current_working_directory
• fs.path.normalize(path: string)
• support for @self and new init.luau require resolution semantics (both are supported, seal will fallback to the new semantics if a module isn't found)
• require resolution takes into account all .luaurcs, not just the closest one
• --version
• --help actually displays helpful stuff now, though it's a wip
• update to latest mlua 0.10.3 (latest git commit) which fixes issues with integer interop
• pcall return type now typed as (boolean, T | error) to (somewhat) better represent errors in mlua. (note that typeof(err) still returns userdata and i'll look into fixing that later)

Fixes

• rewrote require resolver; requires should now work like they're supposed to and be well tested
• seal run not assigning the correct chunk debug names, same issue as running files with seal without a ./ prefix
• lots of really weird edge cases with UNC paths on windows (like \\?\C:\Users...) affecting pathlib functions and require resolution on windows
• process.shell on Windows and various bugs with it and process.run
• big numbers incorrectly serializing to mlua LuaNumbers instead of LuaInteger

seal v0.0.4-rc.1

First published release of seal!

This includes the new fs APIs from the fs-rewrite, as well as most features for simple general purpose scripting.