chore: fix semantic-release configuration and bootstrap v0.1.0 tag

[ckrough]

Summary

This PR fixes the semantic-release GitHub Actions workflow failure by:

• Creating the initial v0.1.0 git tag at commit f5f5c52
• Fixing the deprecation warning in semantic-release configuration

Background

The release workflow was failing with:

No tags found with format 'v{version}' couldn't identify latest version

Root cause: semantic-release requires at least one existing tag to calculate version bumps, but the repository had no tags.

Changes

1. Created v0.1.0 Tag

• Tagged commit f5f5c52 (2025-12-22) as v0.1.0
• This was the last commit with version 0.1.0 before the bump to 0.2.0
• Matches the CHANGELOG.md entry for v0.1.0
• Tag has been pushed to establish the baseline for future releases

2. Fixed Deprecation Warning

• Moved changelog_file from [tool.semantic_release.changelog] to [tool.semantic_release.changelog.default_templates]
• Prevents deprecation warning in python-semantic-release 9.x
• Ensures compatibility with future v10 release

Testing

• ✅ v0.1.0 tag created and pushed successfully
• ✅ Tag points to correct commit f5f5c52
• ✅ Configuration change eliminates deprecation warning
• ⏳ GitHub Actions workflow will verify on merge

Expected Outcome

After merging:

• ✅ Release workflow will pass without errors
• ✅ Future conventional commits to main will trigger automatic releases
• ✅ semantic-release can properly calculate version bumps from v0.1.0 baseline