ci(release): auto-open a python-sdk incorporation issue on release

[rahlk]

Adds a release-workflow job that opens a tracking issue on python-sdk whenever a new version ships, so the consumer's pin and integration get updated.

Motivation and Context

python-sdk consumes codeanalyzer-python as a library and pins it exactly. A release (especially a breaking one like 0.3.0) needs a matching change there. This makes that follow-up automatic instead of manual.

How Has This Been Tested?

YAML validated. The CHANGELOG extraction (awk pulls the section under ## [VERSION] up to the next ## [) was run against the current file and returns the full 0.3.0 section. The cross-repo issue creation cannot run until the token secret exists (see Breaking Changes).

Breaking Changes

None to the package. One setup step: add a repo secret SDK_ISSUE_TOKEN, a PAT (or fine-grained token) with Issues:write on codellm-devkit/python-sdk. Without it, the new job fails, but it is isolated (needs: release), so PyPI and the GitHub Release still succeed. Mirrors the existing HOMEBREW_TAP_TOKEN pattern.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the Codellm-Devkit Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

New job notify-python-sdk:

needs: release
extract: awk the "## [VERSION]" CHANGELOG block into a body file
create: gh issue create --repo codellm-devkit/python-sdk
--title "Incorporate codeanalyzer-python v<version>"
--body-file <changelog section>

Note: GitHub issues are repository-scoped, not branch-scoped, so the issue opens on the python-sdk repo (it cannot target a specific branch).