Use DataView in bindings generation

[dcodeIO]

Given the results of this simple experiment, instead of using short-lived views when accessing memory to work around a possibly detached buffer after a memory.grow, this PR changes memory accesses to utilize a cached DataView (see also), where a try/catch can be and now is used to detect a detached buffer.

There is more that can be done here, like keeping track of where memory might actually grow, and if it's guaranteed to never grow in between two calls of the respective __get/setXY helpers access the DataView directly in subsequent calls. So far this is done where trivial, e.g. in some __lift/lowerXY helpers, but not yet in __lift/lowerRecord where it's a bit unclear whether the additional complexity would actually be worth it.

• I've read the contributing guidelines
• I've added my name and email to the NOTICE file