fix: correct kit package files metadata

[rmi22186]

Summary

• Correct three kit package files entries so published package metadata points to the existing CommonJS bundle names.
• Align the files entries with each package's main and browser fields.

Test plan

• Ran a lightweight Node JSON parse/alignment check for the three changed package files.
• No full build run; metadata-only package.json changes.

[cursor]

PR Summary

Low Risk
Metadata-only package.json changes with no runtime or build logic modifications; low risk aside from ensuring the referenced dist files exist at publish time.

Overview
Fixes npm publish packaging for three web kits by correcting typos in each package’s files array so they match the existing main/browser bundle paths.

Adobe Target: dist/AdobeTarget-Kit.common.jss → dist/AdobeTarget-Kit.common.js.

AdWords: dist/GoogleAdWordsEventForwarder.common..js → dist/GoogleAdWordsEventForwarder.common.js.

GA4 client: dist/GoogleAnalyticsEvent4ForwarderClientSide-Kit.common.js → dist/GoogleAnalytics4EventForwarderClientSide-Kit.common.js.

Without these fixes, published tarballs could omit the actual CommonJS artifacts consumers resolve via main/browser.

^{Reviewed by Cursor Bugbot for commit bc041c9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud