Notebook(Alerts): Zenoss Alert Test Alert uses invalid flux script

_Note_ - for this test we are temporarily using a simple HTTP echo server in EC2 before creating and testing against an actual Zenoss account.

## About the bug

**Steps to reproduce:**
List the minimal actions needed to reproduce the behavior.

1. Setup a listener to receive Zenoss messages.
2. Go to Influxdbv2 UI (note that during this test the feature flag 'notebooksNewEndpoints' was set)
3. Add test data to a bucket
4. Create an Alert Notebook
5. Use the test data to define the query
6. In the alert section choose Zenoss
7. Add a the username, password, severity, action and Method
8. Click "Test Alert"

**Expected behavior:**

Expected to receive an alert message in the listener

**Actual behavior:**

An error notification appears "Failed to send alert to zenoss. Please try again."
In the Developer Tools networking console the return value was 400.
Copying the flux script payload into the Explorer window shows that the script is invalid.

**Visual Proof:**

_screencast_

_Generated flux script in explorer _

## About your environment

**Environment info:**

Testing against K8SIDPE remocal.

Latest commit in UI Project
```
commit a832ae6f4e4979fced6e44fb2cc955afa05fa3f6 (HEAD -> master, upstream/master, origin/master, origin/HEAD)
Author: asalem1 <19984220+asalem1@users.noreply.github.com>
Date: Thu Feb 10 13:02:46 2022 -0800

```
Latest commit in K8SIDPE
```
commit 68fd2e73d645a0aad1f7075a61a411b4adbe08b1 (HEAD -> master, origin/master, origin/alchemy/automatic, origin/HEAD)
Author: Hercules Mango Churchill
Date: Thu Feb 10 05:11:06 2022 +0000

```