[BUG] Pipedream connect proxy does not support OAuth 1.0

**Describe the bug**
Requests to trello using the connect proxy endpoint don't work.

**To Reproduce**
1. Make a connect proxy request using a trello app, ex. GET https://api.trello.com/1/members/me/boards

**Expected behavior**
It works

**Screenshots**
N/A

**Additional context**
See slack conversation here: https://pipedream-users.slack.com/archives/CPTJYRY5A/p1758823092227789

Copied for context:
Eduardo Fungairino
[Yesterday at 1:58 PM](https://pipedream-users.slack.com/archives/CPTJYRY5A/p1758823092227789)
I'm testing out the proxy endpoint using a trello integration, but it looks like the query params that Trello expects into the url are not being set?
I get back a 400 bad request, 'invalid token' response text, which seems to come from Trello.
My request looks like:
GET 'https://api.pipedream.com/v1/connect//proxy/LzEvbWVtYmVycy9tZS9ib2FyZHM=?account_id=&external_user_id=
Headers

Eduardo Fungairino
[Yesterday at 2:09 PM](https://pipedream-users.slack.com/archives/CPTJYRY5A/p1758823784130879?thread_ts=1758823092.227789&cid=CPTJYRY5A)
How exactly does Pipedream know where to add the expected parameters in the proxy url? Trello apparently needs key={yourKey}&token={yourToken}'
https://developer.atlassian.com/cloud/trello/guides/rest-api/api-introduction/#authentication-and-authorization

Danny Roosevelt (Pipedream)
[Yesterday at 2:51 PM](https://pipedream-users.slack.com/archives/CPTJYRY5A/p1758826319962909?thread_ts=1758823092.227789&cid=CPTJYRY5A)
This may be related to Trello using OAuth 1.0 instead of 2.0, which is pretty non-standard, but I'm checking it out.

Eduardo Fungairino
[Today at 1:54 PM](https://pipedream-users.slack.com/archives/CPTJYRY5A/p1758909254609689?thread_ts=1758823092.227789&cid=CPTJYRY5A)
Any update on this? I can create a bug issue if needed

Danny Roosevelt (Pipedream)
[9 minutes ago](https://pipedream-users.slack.com/archives/CPTJYRY5A/p1758913600208779?thread_ts=1758823092.227789&cid=CPTJYRY5A)
Yea I did get a chance to dig in, and unfortunately OAuth 1.0 isn't supported in the Connect Proxy right now (there are very few apps that still rely on it). Feel free to create an issue in GH and we can track it there.