Integration Request: ScrapeUnblocker (web scraping / anti-bot unblocker)

### Required Pre-requisites

- [x] I have read the [Documentation](https://www.aci.dev/docs)
- [x] I have searched the [Issue Tracker](https://github.com/aipotheosis-labs/aci/issues)
- [x] I have searched the [apps directory](https://github.com/aipotheosis-labs/aci/tree/main/backend/apps) to see if this integration already exists

### App Name

ScrapeUnblocker

### Function Name

scrape_website, search_google

### API Docs Link

https://developers.scrapeunblocker.com

### Additional Context

ScrapeUnblocker is a web scraping / anti-bot unblocking API (Cloudflare, DataDome, PerimeterX, Akamai). It renders pages behind anti-bot protections and returns HTML or AI-parsed JSON, plus a Google SERP endpoint. This is the same integration category you already ship for firecrawl, brightdata, scrapfly, scrapingbee, etc.

The integration code is already fully prepared:
- scrape_website (POST /getPageSource) - returns page HTML or parsed JSON
- search_google - Google SERP results
Both use header auth (X-ScrapeUnblocker-Key), following your existing apps/ structure. Branch (GitHub shows "Able to merge"): https://github.com/ScrapeUnblocker/aci/tree/scrapeunblocker-integration

We could not open a PR directly because the repo restricts PRs to collaborators only. Could you either pull this branch in, or grant collaborator access so we can open the PR ourselves? Happy to adjust to any conventions you prefer. Thanks!

Review the existing integration branch and compare it with the repository's backend/apps/ structure and existing scraping integrations. Check the scrape_website and search_google entry points against the ScrapeUnblocker API documentation, then verify that both functions use the expected header authentication and endpoints before determining whether the integration is ready to include.

Escrito por el modelo de indexación a partir del texto del issue.