chore: try using a well-known deno_cache for automated web bundle

[KnightNiwrem]

It could be the case that bundling fails as the tightly restricted list of directory for --allow-write meant that deno could not write to deno cache, as it is not specified.

This PR attempts to specify a well-known path for deno cache so that it can be specified in the list of directory for --allow-write, in an attempt to resolve the current build error.

[KnorpelSenf]

LGTM, just a nit. Also, please don't mess with the version numbers :D

[KnorpelSenf]

Does this fix out previous problem? In other words, should it close #343?

[codecov-commenter]

Codecov Report

Base: 36.93% // Head: 36.93% // No change to project coverage 👍

Coverage data is based on head (b1af957) compared to base (2678048).
Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #344   +/-   ##
=======================================
  Coverage   36.93%   36.93%           
=======================================
  Files          17       17           
  Lines        4364     4364           
  Branches      157      157           
=======================================
  Hits         1612     1612           
  Misses       2750     2750           
  Partials        2        2           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[KnightNiwrem]

Does this fix out previous problem? In other words, should it close #343?

I guess we will only truly know when we let GH Action run it. But at the very least, locally, this setup no longer produces any additional write permission prompts.

[KnorpelSenf]

Let me rephrase: were missing write permissions what caused the error?

[KnorpelSenf]

But well, we can merge this before #343 and just try. Today is the day of patch releases.

[KnorpelSenf]

TYSM!