Bring back modern angular builder for dotcms-ui

[fmontes]

Proposed Changes

• change 1
• change 2

Checklist

• Tests
• Translations
• Security Implications Contemplated (add notes if applicable)

Additional Info

** any additional useful context or info **

Screenshots

Original	Updated
** original screenshot **	** updated screenshot **

[github-actions]

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Edit this PR description and add one of these lines:

• This PR fixes #123 or Fixes: #123

• This PR closes #123 or Closes: #123

• This PR resolves #123 or Resolves: #123

• Other supported keywords: fix, fixed, close, closed, resolve, resolved
  Option 2: Link via GitHub UI (Note: won't clear the failed check)

1. Go to the PR → Development section (right sidebar)

2. Click "Link issue" and select an existing issue

3. Push a new commit or re-run the workflow to clear the failed check
   Option 3: Use branch naming
   Create a new branch with one of these patterns:

• 123-feature-description (number at start)

• issue-123-feature-description (issue-number at start)

• feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.---

This comment was automatically generated by the issue linking workflow

[Copilot]

Pull request overview

This PR updates the dotcms-ui Nx target configuration to use Angular’s modern application builder instead of the Nx browser-esbuild executor, aligning the app build with the Angular CLI-style builder setup.

Changes:

• Switch dotcms-ui build target executor to @angular-devkit/build-angular:application.
• Reshape key build options (entrypoint key from main → browser, polyfills to array, outputPath to object form).
• Remove previously configured global scripts entries (now an empty array).

[Copilot]

outputs is set to {options.outputPath.base}, but outputPath is not consistently an object across configurations (e.g., development overrides it with a string). This can break Nx output tracking/caching and may fail option validation depending on the builder schema. Keep outputPath the same type in all configurations (either always a string, or always an object) and make outputs reference the correct path accordingly.

[Copilot]

Because the base options.outputPath was changed to an object, this development configuration now overrides outputPath with a string, creating an inconsistent option type across configurations. This can lead to builder schema validation errors and also makes the target's outputs ({options.outputPath.base}) invalid for the development build. Align development.outputPath with the same object shape (or keep outputPath as a string everywhere).