fix: semantic release should only build PyPI packages, not containers

[fgogolli]

Description

Fix semantic release workflow to follow single responsibility principle by only building PyPI packages instead of containers and documentation.

Type of Change

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

Related Issues

Fixes semantic release, SBOM, and container build workflow failures on main branch.

How Has This Been Tested?

• Manual testing performed
• Analysis of workflow logs and configuration files
• Verification of workflow trigger sequences 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 calling orchestrator.sh which built containers with wrong versions and wrong registry.

Solution: Change build_command from orchestrator.sh to 'make build' to only handle PyPI packages.

Impact:

• Semantic Release workflow: Only version bumping + PyPI publishing
• Container Build workflow: Handles containers separately on release events
• Docs workflow: Handles documentation separately

Performance Impact

• Performance improved
• Workflows now run independently and can be debugged separately

Security Considerations

• No security implications

Dependencies

None

Deployment Notes

This change will allow the 1.0.0 release to proceed successfully with proper version consistency across all workflows.