[BUG] Gleap app auth is misconfigured — asks for username + password, Gleap only supports an API key

**Describe the bug**

The Gleap app on Pipedream can't be connected. Its auth configuration asks for an
API key **and** a username + password. Gleap has no username/password (basic auth)
login for its API — the only credential is an API key issued per project. There are
no valid values to enter in those two fields, so the "Connect account" step can never
be completed, which makes every Gleap action and trigger unusable.

I'm on the Gleap team — happy to provide a test project and review the fix.

**What Gleap is (for context)**

Gleap (https://gleap.io) is a customer feedback and support platform: in-app bug
reporting with screenshots and screen recordings, session replay, live chat, surveys,
a help center, and an AI support agent. The public API lives at `https://api.gleap.io`
and authenticates with an API key sent as a request header. Keys are generated in the
Gleap dashboard under Project settings → API. There is no user login, no basic auth,
and no OAuth username/password flow for API access.

**To Reproduce**

1. In a Pipedream workflow, add any Gleap action (or search "Gleap" under
Accounts → Connect an account)
2. The connect dialog requires: API key, Username, Password
3. Enter a valid Gleap API key and leave username/password empty → the form can't be
submitted
4. Enter dummy values for username/password → the account connects but every request
fails auth

**Expected behavior**

The Gleap app should use a key-based auth strategy with a **single** custom field:

- `api_key` — the project API key from the Gleap dashboard

**Additional context**

Gleap API docs: https://docs.gleap.io — the API reference has the exact auth header
and the full endpoint list. You can reach us at hello@gleap.io or via https://gleap.io
if it's easier to sort the correct auth config directly with us.

Start from the Gleap app entry used by Accounts → Connect an account and inspect its authentication configuration. Compare it with the Gleap API documentation and reproduce the connection flow; done means the form requests only api_key and a valid key allows Gleap actions and triggers to authenticate.

Written by the indexing model from the issue text.