ci: SDKE-548 add CI/CD and semantic release

[jaissica12]

Instructions

1. PR target branch should be against development
2. PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
3. PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary

• Added semantic-release “Release Kit” workflow and removed legacy deployment.
• Automated versioning, changelog, npm publish, and GitHub release assets.

Testing Plan

• Was this tested locally? If not, explain why.
• {explain how this has been tested, and what, if any, additional testing should be done}

Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)

• Closes https://rokt.atlassian.net/browse/SDKE-548

[rmi22186]

Suggested change

	assets: ['dist/FacebookEventForwarder.common.js', 'dist/FacebookEventForwarder.iife.js'],
	assets: ['dist/FacebookEventForwarder.common.js', 'dist/FacebookEventForwarder.iife.js', 'FacebookEventForwarder.esm.js'],

[rmi22186]

you wouldn't have known this, but I was looking in our commit history and looks like someone added the ESM module to the rollup config as an output, so we should include it. this is something we should do for all our other kits as well.

[jaissica12]

Sure, I'll review the other kits for ESM outputs and open Sustained Engineering tickets for any that are missing it

[rmi22186]

one minor comment but otherwise LGTM.