Parallelize Release and Benchmark Process

[bdemann]

The release process has a giant bottle neck in the form of going though each of the examples and updating it to the next version of Azle. I had an idea where we parallelize it by spinning each one up into it's own job, the result is committed to a unique branch, and then after all of those steps are finalized spinning up one more job that will go through each of those branches and merge them back into the release branch.

The initial prototype indicates that this in fact possible! So we want to make a new release process that will:

• [ ] update candid
• [ ] run benchmarks
• [ ] update package.json dependencies
  • [x] set Azle to the next version
  • [ ] make sure other dependencies are up-to-date like the agent, ts, etc
• [ ] update package-lock with the new stuff from above

As long as we are at it we may want to look into updating Azle's:

• [ ] package.json
• [ ] Cargo.toml
• [ ] corresponding lock files

Other things to do

• [ ] Make a PAT and add it to the secrets with proper security

[bdemann]

I am blocked on this until we can create a PAT