feat: add sql endpoint for tinybird queryActvitites, for preventing 414

[ulemons]

What

Use the SQL API on Tinybird as described in the official documentation.
This allows us to send queries via POST with a JSON body instead of long GET requests.

Why

When using the standard /v0/pipes/<pipe>.json GET approach, Tinybird can return a 414 (URI Too Long) error if the request contains too many query parameters — for example, when passing large arrays.

How

1. Added a new pipeSql method to the tinybirdClient, using POST /v0/sql.
2. Updated the parameter builder to correctly handle arrays and preserve their types in the JSON body.
3. (Optional) Normalized the Tinybird response to match the existing pipe method shape for consistency.

[joanagmaia]

LGTM ✅

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.