feat: Google Cloud Storage bucket uploads

[mattes]

Changes in this PR:

• move *.wasm file into parent, delete *_js directory.
• Increase artifact lifespan to 14 days
• Release workflow also uploads to Google Cloud Storage bucket

Files uploaded to Google Cloud Storage bucket are individually gzip'ed with flag -7 to go with a slightly higher/ better compression at the cost of decompression speed. The gzip default is 6 btw.

Files can be accessed via https://web-prover-circuits.pluto.xyz/<git-hash>/file. An example URL format would be:

https://web-prover-circuits.pluto.xyz/4e342aa123f1ba339875d5efacb4c9b225b3f6ec/http_verification_1024b.bin

When a browser requests a file, it typically includes the header Accept-Encoding: gzip. In response, the server returns the gzipped content, which the browser automatically decompresses on the fly and presents to the developer as an uncompressed file.

Similarly, a non-browser client should include the Accept-Encoding: gzip header in its request to download the gzipped file. If this header is not included, Google Cloud Storage will serve the decompressed version of the file.

To illustrate this behavior more clearly, consider the following examples:

# Download the gzipped file
curl -v "https://web-prover-circuits.pluto.xyz/<githash>/http_verification_1024b.bin" -H "Accept-Encoding: gzip" > http_verification_1024b.bin.gz

# Download the decompressed file
curl -v "https://web-prover-circuits.pluto.xyz/<githash>/http_verification_1024b.bin" > http_verification_1024b.bin

Closes #92

[devloper]

LGTM