feat: Create a compiled release package

[OulipianSummer]

What is it?

• Feature / enhancement
• Bug
• Docs / tests

Description

This is an initial step towards resolving #680.

This pull request adds a build step onto the build.prod command that creates a lib.tar.gz file with the compiled code, but is gitignored, so it doesn't make its way back into the repo.

What is missing is a github/changeset step that uploads that file to the tagged github release. This is something I don't have good insight on. The changeset build step uploads the compiled code to npm. When I test this build process on my fork, the ci jobs fail because I don't have access to the npm pipeline, which is good. However, it makes it hard to debug this.

This issue changesets/changesets#1366 seems to offer a solid guide on how to do this using a separate action.

Use cases and why

Resolves an ongoing issue where the partytown library is not released via github as a compiled asset.

Checklist:

• My code follows the developer guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• Added new tests to cover the fix / functionality

[changeset-bot]

🦋 Changeset detected

Latest commit: 5ba71ed

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@qwik.dev/partytown	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[OulipianSummer]

Opening this for review. My ability to test the CI workflow itself is limited, but this configuration should upload a compiled lib archive to the release.

I lack the insight to know exactly how this would function in your CI pipeline, so any eyes on this to spot any obvious bugs would be appreciated.

There is a failed lint job that appears to be an upstream issue with the work on main, but it is not related to this work.