Add capability for property tests on buffers and strings about clarity-wasm HOT 3 CLOSED

I added a Strategy for generating buff in my PR #131.

For the hack, from what I understand, it's not great, but not terrible either.
Apparently, the issue is that the store is not reset between tests. And since we write in the memory for those types, it means that there are remaining artifacts from the former tests in the current one.
That is not necessary an issue if we keep using the memory with our current model: predetermined offset for computed values and stacks-pointer for computation space. However, it is not great for repeatability. Maybe one day, we'll have randomly a configuration that makes a test fail, but we won't be able to replicate it because it came from a series of random events.

However, I believe this is a fact we should just accept for our tests, or the time needed to execute them will drastically increase if we have to create a new store hundredth of times per per tests.

from clarity-wasm.

@Acaccia Is this still needed?

from clarity-wasm.

@smcclellan Nope, it’s done.

from clarity-wasm.