Assert heap function after release

[peterpeterparker]

Motivation

Deploying the Juno website went over heap size and therefore could not be upgraded. I had to reset. I should double check if the heap size assertion is performed in the Console UI, in the upgrade wizard.

[peterpeterparker]

Also check the Console!

[peterpeterparker]

We are not checking in the upgrade because, the upgrade will throw an error because of the heap.

I double checked the CLI, it still does the assertion, likewise for the GitHub Action.

https://github.com/peterpeterparker/cycles.watch/actions/runs/16770587591/job/47484572909

Though I'll improve that part by throwing an error if headless.

[peterpeterparker]

Satellites are still spinned with 1 GB of heap limit.
I added an assertion to the deploy assest of the Console UI.
I also added the display of the memory on cycles.watch so that I keep an eye on it.

[peterpeterparker]

I also released a new version of the CLI and GitHub Action (https://github.com/junobuild/juno-action/releases/tag/v0.4.9) which exit(1) instead of blocking when the assertion is reached. So I think I've controlled everything.