Add support for webassembly_binding in cloudflare_worker_script

[ldesgoui]

This remains a draft for now because I have not tested beyond running make test, I will attempt to make it run with terraform, I am quite new with the tool, so it may take some time.

Closes #178

cc @jacobbednarz

[ldesgoui]

I found how to run acceptance tests, the worker does properly contain the 15 byte wasm module, as expected:

[nix-shell:~/terraform-provider-cloudflare]$ TF_ACC=1 go test -v github.com/cloudflare/terraform-provider-cloudflare/cloudflare -run TestAccCloudflareWorkerScript
=== RUN   TestAccCloudflareWorkerScript_Import
--- PASS: TestAccCloudflareWorkerScript_Import (18.05s)
=== RUN   TestAccCloudflareWorkerScript_MultiScriptEnt
=== PAUSE TestAccCloudflareWorkerScript_MultiScriptEnt
=== CONT  TestAccCloudflareWorkerScript_MultiScriptEnt
--- PASS: TestAccCloudflareWorkerScript_MultiScriptEnt (37.41s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/cloudflare	55.469s

[ldesgoui]

Should I update CHANGELOG.md?

[jacobbednarz]

I find the schema name here a little lacking; what are your thoughts on using something more aligned with the existing schema fields but still convey it's base64 encoded, like base64_encoded_text? We could also reuse text here and note in the documentation it is the bas64 encoded value?

[ldesgoui]

Hm, I'm not particularly happy with the notion of "text" either, what's actually supposed to be here is a wasm module, which is binary data. module probably works best, changing it.

[jacobbednarz]

How about data? module leaves some ambiguity for a novice like me.

[ldesgoui]

It feels like data would be more ambiguous than module, the latter being defined in spec to be this exact thing

[ldesgoui]

Is this still a point of contention? I can deal with it being data data

[jacobbednarz]

No point of contention from me, just want this make sense to those that are going to be using it. I have little experience here so happy to leave as-is for your wording.

[jacobbednarz]

Thanks for the quick turn around @ldesgoui! No need to update the CHANGELOG, we'll drop that in once it lands to avoid resolving merge conflicts for it within your branch.

[jacobbednarz]

integration suite is all green 🍏 thanks for this!