fix: disable PyPI publishing in semantic-release configuration

[fgogolli]

Description

Fix semantic-release workflow by disabling PyPI publishing and letting the dedicated publish workflow handle PyPI publishing with proper OIDC authentication.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• CI/CD or build process changes

Related Issues

Fixes 401 Unauthorized error in semantic-release workflow when attempting to publish to PyPI without OIDC permissions.

How Has This Been Tested?

• Manual testing performed
• Analysis of semantic-release configuration and workflow logs
• Verification of workflow separation and responsibilities

Test Configuration

• Python version: 3.11-3.14
• OS: Ubuntu (GitHub Actions)
• AWS region: N/A
• Dependencies changed: None

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• My changes generate no new warnings
• Any dependent changes have been merged and published

Additional Notes

Root Cause: Semantic-release was trying to publish to PyPI but lacks OIDC authentication permissions. Only the publish.yml workflow has proper OIDC setup.

Solution: Add [tool.semantic_release.publish] dist = false to disable PyPI publishing in semantic-release.

New Workflow Responsibilities:

• Semantic Release: Version bumping + GitHub release creation
• Publish Workflow: PyPI publishing with OIDC (triggered by GitHub release)
• Container Build: Container publishing (triggered by GitHub release)

Performance Impact

• Performance improved
• Workflows now have clear separation of responsibilities

Security Considerations

• Security improved
• Uses proper OIDC authentication for PyPI publishing instead of attempting unauthorized access

Dependencies

None

Deployment Notes

This change will allow semantic-release to complete successfully by only handling version management and GitHub releases, while PyPI publishing is handled by the dedicated workflow with proper OIDC permissions.