VRL Running inside WASM does not have the correct clock

[Scott Opell]

Have not investigated, but running the v10 example project yields the following output:

{ "message": "Hello VRL", "status": "success", "timestamp": t'2022-01-01T00:00:00Z' }

That timestamp field is populated from a call to now which is obviously wrong.

I suspect we'll need to track down which calls VRL is making to get the time and see if how wazero/wasi implements that call.