chore(ci): add automated dev releases

[rwaskiewicz]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally and any changes were pushed
• Tests (npm test) were run locally and passed
• Prettier (npm run prettier) was run locally and passed

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Dev releases don't exactly exist for this project. Prereleases are cut and published to the npm registry.

GitHub Issue Number: N/A

What is the new behavior?

this commit implements an initial workflow for dev releases for stencil
sass. it is capable of:

• generating a build based using the same logic as other ci workflows
• generating a dev build version
• invoking a publish action with the dev version & 'dev' tag

a new publish action is added that is capable of incrementing the
version of the package and publishing changes to npm has been added. the
intent is to reuse this in some capacity for production releases.

this commit also includes additional actions for building the project &
downloading/uploading archives. to date, ci has been rather simplistic
in this repo. however, it's planned to integrate these actions into
existing workflows once this has been added to main.

Does this introduce a breaking change?

• Yes
• No

Testing

In a73de0c, I had a push event trigger enabled such that when I pushed this branch to GitHub, a dev build would get triggered. I considered this to be safe because:

1. It built off the same workflow/steps as the create-stencil cli, which has dev releases
2. I tested this without publishes enabled at first (commented out) - but I've squashed that commit away since then
3. I figured worst case, since I verified the tag and version number, I'd push a bad dev release to npm
4. https://github.com/ionic-team/stencil-sass/actions/runs/7668967472 shows a successful publish to the npm registry

I also ran the Framework CI workflow using a dev build of stencil sass, which passed https://github.com/ionic-team/ionic-framework/actions/runs/7669946636

Other information

[christian-bromann]

A lot of pipeline code seems very similar to the @stencil/store project. I think there is a way to define these actions in a separate repository and commonly use them across multiple projects. I guess another Jedi day project 😉

LGTM 👍

[tanner-reits]

Yep, the same as our other workflows (for the most part). Time for a monorepo! 😂