chore(PROC-1514): release v1.0.0 and remove release-as pin

[CalNightingale]

Linear: https://linear.app/gradienthealth/issue/PROC-1514/adopt-release-please-for-cloud-optimized-dicom

Summary

Remove the release-as: 1.0.0 pin from release-please-config.json so subsequent releases are derived from Conventional Commit types as intended. The Release-As: 1.0.0 commit footer below forces release-please to open the 1.0.0 Release PR off this commit, since the previous ci(PROC-1514): commit is non-user-facing and doesn't on its own trigger a release.

Context

PR #97 wired up release-please but its merge commit was ci: — release-please classifies that as non-user-facing and skipped opening a Release PR. A v1.0.0 tag was cut manually, but pyproject.toml was still 0.2.5 at that commit, so the publish workflow built a 0.2.5 wheel that PyPI rejected (already existed). The tag has been deleted.

This PR gets the release flowing correctly. Important: when squash-merging, keep the Release-As: 1.0.0 footer in the squash-commit message — release-please reads it from the commit on main.

Release-As: 1.0.0

Test plan

• Squash-merge preserving the Release-As: 1.0.0 footer
• release-please opens a "chore(main): release 1.0.0" PR
• Merge Release PR → v1.0.0 tag created, pyproject.toml = 1.0.0
• publish.yml fires on tag → 1.0.0 wheel uploaded to PyPI