chore: add automated release workflow for module tags

[blink-so]

This PR adds a GitHub Actions workflow that automatically creates releases when module tags are pushed to the repository.

Features

• Triggers on module tags: Responds to tags matching release/<namespace>/<module>/v*.*.* pattern
• Module-specific changelogs: Filters changelog to show only changes affecting the specific module
• Smart PR detection: Extracts PR numbers from commit messages in various formats
• GitHub username resolution: Attempts to resolve GitHub usernames from commits using multiple methods
• Automated release creation: Creates GitHub releases with proper titles and formatted changelogs

Example Usage

When you push a tag like release/coder-labs/sourcegraph-amp/v1.0.1, the workflow will:

1. Extract the namespace (coder-labs), module (sourcegraph-amp), and version (v1.0.1)
2. Find the previous tag for that specific module (e.g., release/coder-labs/sourcegraph-amp/v1.0.0)
3. Generate a changelog showing only commits that affected registry/coder-labs/modules/sourcegraph-amp/
4. Create a GitHub release titled "coder-labs/sourcegraph-amp v1.0.1" with the filtered changelog

Changelog Format

The generated changelog will look like:

## What's Changed

* fix: update Sourcegraph AMP source URL by @matifali in https://github.com/coder/registry/pull/370

**Full Changelog**: https://github.com/coder/registry/compare/release/coder-labs/sourcegraph-amp/v1.0.0...release/coder-labs/sourcegraph-amp/v1.0.1

This ensures that each module's release only shows relevant changes, making it easier for users to understand what changed in their specific module.

Testing

The workflow has been tested with the existing tag pattern and module structure. It correctly parses tags, identifies module paths, and generates appropriate changelogs.

[blink-so]

The CI failure is unrelated to this PR - it's a network/SSL issue in the cursor-cli module test where the Cursor installer can't connect to cursor.com:443:

curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to cursor.com:443

This is a transient infrastructure issue in the CI environment, not caused by the release workflow changes. The workflow file itself is valid and ready for review.

[Copilot]

Pull Request Overview

This PR adds a GitHub Actions workflow to automatically create releases when module tags are pushed to the repository. The workflow filters changelogs to show only changes relevant to the specific module being released.

• Automated release creation for module-specific tags with pattern release/<namespace>/<module>/v*.*.*
• Smart changelog generation that filters commits to only include changes affecting the specific module
• Integration with GitHub's release notes API to extract PR information and resolve usernames

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

If the author is resolved to a name (not a GitHub username), prefixing it with '@' will create an invalid GitHub mention. Only prefix with '@' when .author.login is available, not when falling back to .commit.author.name.

Suggested change

	AUTHOR=$(gh api repos/:owner/:repo/commits/$sha --jq '.author.login // .commit.author.name')
	FILTERED_CHANGELOG="${FILTERED_CHANGELOG}* $COMMIT_MSG by @$AUTHOR\n"
	AUTHOR_LOGIN=$(gh api repos/:owner/:repo/commits/$sha --jq '.author.login')
	if [ -n "$AUTHOR_LOGIN" ]; then
	AUTHOR_MENTION="@$AUTHOR_LOGIN"
	else
	AUTHOR_NAME=$(gh api repos/:owner/:repo/commits/$sha --jq '.commit.author.name')
	AUTHOR_MENTION="$AUTHOR_NAME"
	fi
	FILTERED_CHANGELOG="${FILTERED_CHANGELOG}* $COMMIT_MSG by $AUTHOR_MENTION\n"