Azle 0.26.0 (possibly release candidate for Azle 1.0)

[lastmjs]

Features

• fix all process.env.principal things, use a class instance variable instead of a function that throws
• in the class-based syntax, can you allow multiple classes in multiple files? Do we even need to export the class?
• azle should work within npm workspaces...study workspaces deeply
  • will npm exec --offline azle work?
• Automatically generating Azle-included canister definitions #2320
• Can we add Mac and WSL tests? We now have 500 concurrents...I say we should do that on release
• Finish the dfx azle new sdk PR
• Finish the candid PR for generating canister bindings automatically: Exporting of IDL objects from js target. ts-js target added dfinity/candid#575
• Add to our daily run updating everything
  • node
  • dfx
  • wasi2ic
  • rust
  • canister bindings
• sending a u64 for clearTimer, setTimer, and setTimerInterval did not work. Create a minimally reproducible example and open an issue with rquickjs...it kept trying to convert to an f64 for some reason...or maybe that's what bigints convert into to cover all cases?
• Make sure that all rquickjs number conversions will be done accurately...we might want to go back to strings for all numbers if rquickjs won't correctly convert between number, bigint, and the Rust number types
• Check that all ic APIs return Uint8Arrays
• Check that all IC APIs are perfect in their documentation, future-proofness, and type conversions and typescript types
• All types in Azle stable ic APIs need to be manually checked to ensure the TypeScript type and value type actually match
• run the fuzz tests for 5-6 hours, check for any failing tests, manually inspect each test's last output to see if there are any memory leak concerns
• How are we dealing with the random seed now in rquickjs? And in wasmedge-quickjs? We have randomness tests right?
• Open rquickjs issue about Context or Ctx
• simple recursion in Rust seemed to take forever to reach the instruction limit for some reason...is this a DOS vector?
• Should we always run fuzz tests on release or pr or something?
• call_raw has an unreachable after about 30 minutes (seems intermittent, do not ignore this)
• 5 hour fuzz tests are hitting unreachable errors at least in call_raw and candid_encoding
• Add call delay 0 fuzz tests
• Add multi-process fuzz tests
• Add automatic fuzz tests
• Benchmarks need to be automatically updated on every release
• All things need to be updated automatically, we need to minimize manual updates of dependencies and benchmarks and ANYTHING
• The PR created on a release candidate should be a draft pr?
• was node updated in our GitHub actions appropriately?
• Use the official dfx extension installation from file process if it exists now
• reopen all issues from the property testing phase...I thougth they were obsolete, mostly the recursive ones...but not all of them are because we are using IDL under-the-hood
• Critical: if you install multiple versions of Azle in one project, the global setters might overwrite eachother
  • deeply think about global variables and the fact that azle can be executed multiple times if there are different versions

Breaking Changes

• print has been removed from azle and ic from azle/experimental. console should be used instead
• argDataRaw has been renamed to msgArgData

Documentationn

• Add inReplicatedExecution api
• argDataRaw has been renamed to msgArgData