Add regression test for non-canonical path shapes

Extends the same-path guard coverage with a case where localOutputDir
and bundleOutputDir are string-distinct but resolve to the same
directory (`/test/extension/dist` vs `/test/./extension/dist`). This
is the actual shape that triggered the original fs-extra "Source and
destination must not be the same" failure in the field — the existing
identical-strings test did not catch it because both the old and new
guard handle the trivial case.

Verified that this test fails against the pre-fix guard (`copyFile`
is called with distinct strings) and passes once the guard normalizes
both sides with `resolvePath`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: vctrchu

packages/app/src/cli/services/build/steps/bundle-ui-step.test.ts

@@ -57,4 +57,19 @@ describe('executeBundleUIStep', () => {
     // Then
     expect(fs.copyFile).toHaveBeenCalledWith('/test/extension/dist', '/bundle/handle')
   })
+
+  test('skips the copy when local and bundle output directories resolve to the same path but differ as strings', async () => {
+    // Given — same directory, non-canonical string shape (`.` segment).
+    // Without path normalization in the guard, the raw string comparison
+    // would fail and fs-extra would throw "Source and destination must not
+    // be the same" on the downstream copy.
+    mockContext.extension.outputPath = '/test/./extension/dist/handle.js'
+    vi.mocked(buildExtension.buildUIExtension).mockResolvedValue('/test/extension/dist/handle.js')
+
+    // When
+    await executeBundleUIStep(step, mockContext)
+
+    // Then
+    expect(fs.copyFile).not.toHaveBeenCalled()
+  })
 })