feat: Add deployment to smithery

[jirispilka]

• Publishing to Smithery uses a personal account due to group account functionality issues.
• Publication happens through a repository fork at https://github.com/apify-projects/apify-mcp-server since Smithery requires repository write access, which cannot be granted to the main Apify account (https://github.com/apify/apify-mcp-server).
• The fork requires manual synchronization to stay current, as automatic syncing is not configured.
• As of August 22nd, Smithery supports external server publishing with the requirement of an /mcp endpoint.

close https://github.com/apify/ai-team/issues/64

[MQ37]

This sadly breaks the DockerHub integration 🥲

[jirispilka]

Currently, deployment is failing

[MichalKalita]

Info I get from LLM how to use main and module:

- main should point to the CommonJS build (usually in dist/).
- module should point to the ESM build (also in dist/), not to the TypeScript source.
- Both should export the same API.
- Ensure all referenced files are published.

The problem is that we have other exported APIs in the main and module. I think it will break our internal server if Typescript looks at the module and sees only Smithery, not ActorsMcpServer.