chore(CI/CD): Automate extension packaging and release drafting

[dineshsutihar]

Is your feature request related to a problem?

Creating a new release is a manual, multi-step process: updating the version in manifest.json, building the project, packaging the files into a .zip archive, and then manually drafting a new release on GitHub with release notes. This is repetitive and susceptible to human error.

Describe the solution you'd like

1. Create a new GitHub Action workflow that triggers when a new version tag (e.g., v2.2.0) is pushed to the repository.

2. This workflow should automate the entire release process:

• Read the version number from the tag.

• Automatically update the version field in manifest.json.

• Run the build script (npm run build).

• Package the contents of the dist or build directory into a CodeTranslateAI-vX.X.X.zip file.

• Create a new Draft Release on GitHub, attaching the generated .zip file as a release asset.

• (Advanced and Optional) Automatically generate release notes by listing the titles of all pull requests merged since the last release tag.

Additional context

This is a core DevOps improvement that streamlines the release cycle. It saves time, reduces errors, and ensures a consistent release process, which is critical as the project scales.

[singhxabhijeet]

Hey, I'd like to take a look at this for Hacktoberfest. Can I work on this?

[dineshsutihar]

@singhxabhijeet I’ve assigned this issue to you.