fix(braze): point kit homepage URLs at main

[jaissica12]

Background

• These kits live on the v3 line; the npm homepage still linked to master, which 404s.
• Braze kit tracks were first-published from main as @mparticle/web-braze-kit-3 … -6.
• Each kit package.json homepage still used tree/master/…. Those paths do not exist on master (v2), so the GitHub link on the npm package page 404s.
• @mparticle/web-braze-kit-3@3.0.0 is already on npm; npm will not update that version’s metadata. This PR only fixes git so later publishes (4/5/6, and a future 3.0.1) get a working link.

What Has Changed

• Updated homepage in kits/braze/braze-3 … braze-6 package.json from tree/master/ to tree/main/.
• No version bump, no runtime/dist changes.

Screenshots/Video

• N/A

Checklist

• I have performed a self-review of my own code.
• I have made corresponding changes to the documentation.
• I have added tests that prove my fix is effective or that my feature works.
• I have tested this locally.

Additional Notes

• Confirm https://github.com/mParticle/mparticle-web-sdk/tree/main/kits/braze/braze-3#readme loads.
• Merge into main only. Do not merge into master.
• Merge before publishing Braze-4/5/6 so those first npm pages get the correct homepage.
• Braze-3@3.0.0 on npm keeps the old master link until a later 3.0.1.

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

• Closes https://go/j/[ticket-number]

[cursor]

PR Summary

Low Risk
Package metadata-only change with no effect on installed code or runtime behavior.

Overview
Updates the npm homepage field in kits/braze/braze-3 through braze-6 so GitHub links use tree/main/ instead of tree/master/. Those kits are maintained on main; the old URLs 404 on the npm package page.

No version bumps, build output, or runtime behavior changes—metadata only. Already-published versions (e.g. @mparticle/web-braze-kit-3@3.0.0) keep their existing npm metadata until a new publish.

^{Reviewed by Cursor Bugbot for commit 62d2be5. 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