fix(@angular/build): prepend deploy-url to file loader output paths

[maruthang]

PR Checklist

• The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

• Bugfix

What is the current behavior?

Assets processed by esbuild's file loader (e.g., SVGs imported via import svgUrl from './test.svg') do not get the deploy-url prefix applied. This is a regression from the webpack migration.

Issue Number: #32789

What is the new behavior?

Pass the publicPath option through to esbuild's common options so that file loader output paths are correctly prefixed with the deploy-url value (e.g., https://example.com/some/path/media/test.svg).

Does this PR introduce a breaking change?

• Yes
• No

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Code Review

This pull request adds support for prepending the deploy URL to file loader import URLs by passing the publicPath option to the esbuild configuration. A new test case was added to verify that deployUrl is correctly applied to assets handled by the file loader. I have no feedback to provide.