Fix bundling for multiple UI extension should-render targets - #8862

WHY are these changes introduced?

When a UI extension declares should_render for multiple targets, the CLI replaces each condition entry with the next one. The generated conditions bundle registers only the last target, so earlier targets cannot use their declared conditions.

WHAT is this pull request doing?

• Bundles every declared should_render registration into one conditions asset, with distinct generated import names for each target.
• Rejects inconsistent conditions output filenames rather than silently using the first one.
• Adds regression coverage for shared and distinct condition modules, unconditioned targets, older API versions, and filename mismatches.
• Adds an @shopify/app patch changeset.

How to manually test your changes?

1. Use the local CLI to preview an app with a single UI extension that declares two render targets, each with a should_render module.
2. Confirm each target uses its associated condition to control visibility.
3. Repeat with both targets referencing the same condition module, then with separate condition modules.

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
• This is a user-facing bug fix; I've selected a patch bump and added a changeset.