[APP] EnsembleData - Social API

**Name of app / service**
EnsembleData - API for real-time social data scraping

**Link to developer documentation**
- API Documentation : https://ensembledata.com/apis/docs
- Getting started guide: https://ensembledata.com/guide/

Auth note: every endpoint takes the API token as a `token` **query parameter** against the base URL `https://ensembledata.com/apis`, so the app definition would be a single custom API-key field.

**Is lack of support preventing you from moving forward, or do you have a workaround?**
Today the only option is hand-wiring raw HTTP requests, which forces users to work through the API docs and manage authentication in every step themselves. A registry app would let them connect their token once and reuse it across workflows, with each endpoint's parameters surfaced in the action form.

**Are there specific actions or triggers you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!**
1. **TikTok - Get User Info** : `GET /tt/user/info`; takes a `username` and returns the profile and its statistics.
2. **TikTok - Hashtag Search** : `GET /tt/hashtag/posts`; takes a `hashtag` and `cursor`, returns up to 20 posts per call for pagination.
3. **Instagram - Get User Info** : takes a `username`, returns the profile and its statistics.

No trigger is proposed. The API is request/response only with no webhook delivery, so any source would have to be a polling source, and polling would consume units on every check. Better to ship the actions first and let users pair them with a Schedule trigger.

Start with the EnsembleData API documentation and getting-started guide linked in the issue, then verify the listed endpoints: /tt/user/info, /tt/hashtag/posts, and the Instagram user-info endpoint. Done means the three request/response actions expose their stated parameters, reuse one token query parameter, and do not add a polling trigger.

Written by the indexing model from the issue text.