Remove TikTok Trending Capability, Actor, Types, and Args

[rapidfix]

Description

The tiktok trending functionality in tee-worker has been identified as unstable, with reported reliability of only ~50%. It is currently not visible in the UI, and its API integration is underutilized. Given the associated cost of $35/month for miner usage and the lack of reliable output, it is recommended to remove this capability entirely.

Action Items

• Remove the tiktok trending actor implementation.
• Delete related types, arguments, and configuration structs.
• Update scoring logic on subnet-42 to exclude TikTok trending data.
• Remove all documentation references to TikTok trending in docs/ and README.md.
• Update any related test cases or acceptance tests that depend on TikTok.

Background

• The feature has been known to fail intermittently and is not reliable for production use.
• It contributes to unnecessary operational cost ($35/month) without delivering consistent value.
• The feature is already excluded from the UI, so removing it from the backend is a safe and logical step.

Related Issues

• Issue #433 (Error message fix for empty miner responses)
• PR #469 (Acceptance tests updated; tiktok-trending is skipped due to instability)

Notes

• This change should be coordinated with the tee-indexer and data-api-app teams, as downstream dependencies may need updates.
• Consider a deprecation notice before removal if future integration is possible.