ci: use shared tree-sitter release workflow

[anntnzrb]

Summary

Replaces custom release workflow with the shared tree-sitter/workflows reusable workflow.

Closes #136

Changes

• Release artifacts change from platform-specific .so files to .wasm binaries and source tarball
• Releases are no longer created as drafts
• Uses standard tree-sitter release process with build attestations

[anntnzrb]

hi @giacomocavalieri :) - can we get this please?

[giacomocavalieri]

Hello! I'm not the ma maintainer of this package and I don't have the permissions to merge anything :)

[the-mikedavis]

We haven't used this workflow in a while, also see the discussion about not using releases and tags in #100. It's not a hill I'm willing to die on but it's inconvenient for grammar repository maintainers to need to make releases for opencode's sake. The repositories they already use make releases but I don't think it's a common practice for most grammar repositories.

[lpil]

What's the motivation for this work? The changes are listed but not the reasons why

[anntnzrb]

What's the motivation for this work? The changes are listed but not the reasons why

#136

[lpil]

Seems reasonable enough. We would need to pin to a specific hash rather than using main.

Is there a way to do this without doing releases?