Add an e2e test to ensure Go plugins' memory safety

[johnlanni]

Why do you need it?

TinyGo's GC can cause memory leaks in some scenarios, so we changed the GC to https://github.com/wasilibs/nottinygc and solved the memory leak issue (wasilibs/nottinygc#31).

The nottinygc lib is still being iterated frequently and we need to track and test new versions in features. So we need to conduct end-to-end testing to ensure memory safety when upgrading dependencies.

How could it be?

We already have a simple code to detect memory leaks when allocating byte slices of a specific size . We should extend more types of memory allocation (with or without layout, etc.) and add e2e tests for them like other plugins:
https://github.com/alibaba/higress/blob/main/test/e2e/conformance/tests/go-wasm-transformer.go

[rinfx]

apply for this issue