feat: npm and pypi publish workflows

[MDzaja]

This PR introduces two GitHub Actions for automated package publishing:

1. Publish to PyPI: Automates the publishing of Python package to PyPI.
2. Publish to npm: Automates the publishing of TypeScript package to npm.

Both workflows can be triggered either by pushing a Git tag or manually via the GitHub interface. The version for publishing must adhere to one of the following formats: vX.Y, vX.Y.Z, vX.Y.ZaN, vX.Y.ZbN, vX.Y.ZrcN. When triggered manually, the version input should follow the same format. Packages are published without v prefix.

Additional Things to Discuss:

• Author Metadata: The author information in packages/python/pyproject.toml currently uses placeholders and should probably be updated to reflect the Daytona organization ({ name = "dummy", email = "dummy@mail.com" }). Let me know what to write there.

Key Updates:

• Versions in package.json and pyproject.toml are set to 0.0.0 and managed dynamically during the publishing process.
• NPM tags are assigned based on the version suffix:
  • latest for stable releases (e.g., v1.0.0)
  • alpha, beta, release-candidate for pre-releases (e.g., v1.0.0a1, v1.0.0b1, v1.0.0rc1)

Post-Merge Actions:

1. Permissions Setup:

   • Restrict who can manually trigger these workflows.
   • Limit Git tag creation permissions to authorized users.

2. Authentication Setup:

   • PyPI: Register the repository as a Trusted Publisher.
   • npm: Ensure NPM_TOKEN is securely stored in GitHub Secrets.

[Tpuljak]

We follow this convention for pre-releases

v0.0.0-alpha.1
v0.0.0-beta.2
v0.0.0-rc.3

[Tpuljak]

@MDzaja this doesn't seem to be addressed

[Tpuljak]

Change to name = Daytona, email = support@daytona.io