Makes it just that little nicer to use

Since we also expose the Skia-bindings for a Canvas-like API I think it might be a good idea to start refactoring the API to utilise more named arguments e.g. ~x=..., ~y=....

What do you others think?

We currently only test our autoscaling behavior for concurrency and rps. We should add an e2e test that also asserts we properly scale on `

A quick ack of the repo shows whitelist and blacklist referenced in several places. Let's update these references in our code and repo documentation (e.g. README) to use more inclusive terms. Suggestions: allowlist or blockedlist. For references in third-party libs, we can see if there is an updated version of that lib and whether there is any blockers to switching to that version.