Migrate to Apify PyPI organization for package publishing

[vdusek]

Summary

We should start using the Apify PyPI organization for publishing and maintaining our Python packages. This would centralize package ownership under the organization rather than individual accounts.

Motivation

• Centralized ownership of all Apify Python packages under one organization
• Easier management of maintainer access — developers just need their own PyPI accounts and get assigned to the organization
• Reduces bus factor — packages aren't tied to individual accounts
• Better visibility and branding on PyPI

Proposed changes

1. Set up the Apify organization on PyPI (https://github.com/apify/apify-core/issues/25854)
2. Transfer ownership of existing packages (apify, apify-client, apify-shared, etc.) to the organization
3. Developers should create their own PyPI accounts and be added as members of the Apify organization
4. Update CI/CD publishing workflows to use organization-level trusted publishing (or organization API tokens)

Packages to migrate

• apify
• apify-client
• apify-shared
• Any other Apify-maintained Python packages

Notes

• Individual developers should have their own PyPI accounts and be assigned to the organization, rather than sharing credentials
• We should use PyPI's trusted publishing with GitHub Actions where possible