Fix web pixel bundle_ui step

[vividviolet]

WHY are these changes introduced?

The bundle_ui step needs to control where the bundled output is placed, rather than having the output path hardcoded into the relative path returned by getOutputRelativePath.

Before

After

WHAT is this pull request doing?

Moves the dist/ folder prefix from getOutputRelativePath into the bundle_ui step configuration via a bundleFolder config property. This allows the bundling step to own the output directory while getOutputRelativePath returns just the filename (${extension.handle}.js).

How to test your changes?

1. Deploy a web pixel extension and verify the bundled output is still placed in the dist/ folder.
2. Confirm the output file is correctly referenced as ${handle}.js without the dist/ prefix in the relative path.

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• The change is user-facing — I've identified the correct bump type (patch for bug fixes · minor for new features · major for breaking changes) and added a changeset with pnpm changeset add

[vividviolet]

• Fix web pixel bundle_ui step #7398 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.