publish.yaml does not stamp properly

It appears that after https://github.com/bazel-contrib/rules-template/commit/fb992e13e2d205f34ce35496722340a25b11d4e8, stampVersion at https://github.com/bazel-contrib/publish-to-bcr/blob/6a577a5c83afe8461b36f08dd3ca3ab2ac1f12f2/src/domain/module-file.ts#L35 no longer works properly.

Here's a sample stdout from the Github Action:

https://github.com/bazel-contrib/rules_devicetree/actions/runs/16453092376/job/46503690621

```
Loading template files from /tmp/templates-3tj8oi
Creating entry for module version 0.1.1 in bazel-central-registry
Fetching release archive https://github.com/bazel-contrib/rules_devicetree/releases/download/v0.1.1/rules_devicetree-v0.1.1.tar.gz
The release archive's MODULE.bazel version ",
#
# Always leave version unset or set to does not match release version 0.1.1. Creating a version patch.
Successfully created entry for rules_devicetree@0.1.1
```

However, the generated file does NOT have the proper version stamped:

https://github.com/bazelbuild/bazel-central-registry/pull/5315/commits/0e9a7f04c24f30d671f9de57a8a6ecd13a9aa293

It is stamped at the comments:

```
# NOTE:
# version = "0.1.1",
```

So, either stampVersion needs to be fixed, or we need to have an explicit `version = ""` line without the leading `#`.

Start at stampVersion in src/domain/module-file.ts and compare its behavior with the generated MODULE.bazel shown in the issue. Reproduce using the linked GitHub Actions run and release archive. Done means the release version is written to the intended MODULE.bazel version line rather than inserted into the commented template text.

Written by the indexing model from the issue text.