Allow plugin package to be compiled under WASM

[swenson]

Note that it certainly doesn't work under WASM, but at least it should not cause compile errors.

[swenson]

(the builds are failing on 1.17 but are passing anyway because I think the find is hiding the error code?)

[jefferai]

Think you could fix the test?

[swenson]

Sure, let me take a look at find and see if I can fix it.

[swenson]

@jefferai build and tests fixed and will actually fail now when appropriate :)

[jefferai]

Awesome thanks! I will defer to @johanbrandhorst on hitting Approve on this since I've not dealt with wasm and he knows a lot about it :-)

[swenson]

Thanks!

[swenson]

@jefferai would you mind merging?

[jefferai]

A couple of things...

One -- I can't see any reason for the updates the various submodules that only contain go.mod/go.sum updates. Is there a reason, and if not, can they be reverted?

Two -- not all tests are passing, is that expected?

[swenson]

@jefferai

1. hashicorp/go-sockaddr >=1.0.6 is needed to compile to WASM (that is the release after I did Add support for js/wasm go-sockaddr#55)

2. The only test that isn't passing is buf_if_merged, and I honestly haven't investigated what that test is. It appears to be misconfigured (missing token?).

[swenson]

Thanks!