Form Event action fires but submissions never reach HubSpot (same request via curl works)

Nobody has claimed this yet.

We set up a Form Event action on hosted Zaraz (tool created July 2026) with a valid HubSpot form GUID and email/firstname mapped from a `zaraz.track()` call. The debugger and Logpush show the action firing with a clean payload, but no submission ever arrives in HubSpot. Sending the identical body to `api.hsforms.com/submissions/v3/integration/submit/{portal}/{formGuid}` with curl returns 200 and works. This looks a lot like #7, which describes the same pattern for the events action: it fires, but nothing arrives.

Two things we noticed while trying to debug this. They may or may not be the cause:

- `handleFormEvent` calls `manager.fetch()` without awaiting it or checking the response, so if the request fails or never happens, there's nothing to see anywhere. Even just awaiting it and logging non-2xx responses would have saved us a lot of guesswork.
- The manifest gained a required `server_network_requests` permission in 1661a33a (April 2024), but a freshly created tool on hosted Zaraz doesn't show any such permission in the dashboard. We couldn't tell whether the deployed build includes that manifest.

Happy to share debugger captures, Logpush rows, and repro details if useful.

Start at the handleFormEvent entry point and trace its manager.fetch call, then inspect the manifest change in commit 1661a33a for the server_network_requests permission. Reproduce the hosted Form Event submission and compare the request and response with the working curl request. Done means the deployed component reliably reaches HubSpot and failures are observable.

Written by the indexing model from the issue text.