Make @zkfs/examples run against the latest (@latest) deployed packages

[maht0rz]

Update: We use @latest instead of @next now

Since stackblitz doesnt work well with npm workspaces, we can't run @zkfs/examples in stackblitz while using locally built and linked @zkfs/contract-api.

Stackblitz shows @zkfs/examples from the develop branch, but relies on the @next release of our packages. @next packages are released every time a push to develop is made and there are code changes to deploy.

This means there is room for inconsistencies across our CI/CD pipeline, if a deployment of a @next package fails, then stackblitz will point to the latest develop examples but will run older @next packages.

We should make the CI/CD pipeline run @zkfs/examples after publishing @next packages, so that we can be aware of the working status of the stackblitz example.

It won't unpublish/fix the underlying inconsistency, but it will alert us as developers to fix the actual issue with the pipeline.

[maht0rz]

After recent updates, develop is published as @latest (+ canary) and the stackblitz example points to that release as well. However the underlying consistency issue still persists.