Prepare TF-SDK 2.0.0 and publish releases after main merges

Prepares TF-SDK 2.0.0 and makes the reviewed main merge the publication decision.

After the required SDK, Python compatibility, dependency and SRM consumer checks pass, the existing publisher creates v2.0.0 and uploads the exact tested wheel and source archive. Registry checks preserve immutable files and allow safe retries. Develop and MR pipelines keep publication disabled. GitLab Release pages remain with the release owner.

Requires the one-time same-project CI job-token Git-push setting, with existing branch/tag protections and cross-project permissions preserved. No new token, job or manual release step is added.

Verified locally: 398 SDK checks, lint, native GitLab CI Lint for main/develop, and actual tag creation and Twine upload against local-only Git/registry fixtures, including complete/partial retry and conflicting-byte refusal. Final native candidate CI remains pending. The runtime contract stays unchanged. SDK !213 (merged)/!214 (merged) are reviewed separately before the final candidate is frozen.