Packaging metadata points at the stale codeanalyzer-ts repo name

[rahlk]

What's wrong
Two packaging files still point at the repo's old name, codellm-devkit/codeanalyzer-ts. That URL resolves today only because GitHub redirects renamed repositories; it breaks if the old name is ever reclaimed.

1. packaging/python/pyproject.toml:27

   Repository = "https://github.com/codellm-devkit/codeanalyzer-ts"

   This is published package metadata — it becomes the "Repository" link on the package page, so the stale name is user-visible.

2. packaging/homebrew/generate_formula.sh:15,21

   #   REPO=codellm-devkit/codeanalyzer-ts VERSION=0.2.0 \
   #     ./generate_formula.sh ../../release-bins > codeanalyzer-ts.rb
   REPO="${REPO:?set REPO, e.g. codellm-devkit/codeanalyzer-ts}"

   Anyone following the documented example generates a formula pointing at the old name.

To be clear about what is not wrong: codeanalyzer-ts as a tool or binary name is used widely across the org and is fine. The published npm package is codeanalyzer-typescript with bin cants. This issue is only about the two places where the string is an owner/repo reference.

Where
codellm-devkit/codeanalyzer-typescript, files above.

Expected
Both reference codellm-devkit/codeanalyzer-typescript, so nothing depends on the rename redirect.

Additional context
Found during the propagation sweep for codellm-devkit/.github#28, which fixed the same stale reference in the org profile README.

A python-sdk test fixture (tests/resources/typescript/analysis_json/slim/analysis.json) also contains the string, but as recorded path data rather than a link. Not investigated — flagging in case it matters.

Definition of done

• Neither file contains codeanalyzer-ts as an owner/repo reference.
• The next published package's Repository link points at the current repo name without a redirect.