fix(@angular/build): Providing a DI token to dev server for SSR

[klerick]

Add configuration for add custom DI token.

issue: #26323

PR Checklist

Please check to confirm your PR fulfills the following requirements:

• 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

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Add configuration for using custom function for use custom DI token for SSR dev server

Issue Number: 26323

What is the new behavior?

extends angular.json

"ssr": {
          "entry": "path/to/server.ts",
          "providers": "path/to/server-providers.ts"
        },

server-providers.ts

import { REQUEST, RESPONSE } from '@ui-libs/providers';
import { Request, Response } from 'express';

export default (req: Request, res: Response) => [
  {
    provide: REQUEST,
    useValue: req,
  },
  { 
  provide: RESPONSE, 
  useValue: res 
  },
];

Does this PR introduce a breaking change?

• Yes
• No

Other information

[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.

[alan-agius4]

Thanks for your contribution however this implementation does not align the long-term architecture.

We are currently working on a design to solve this problem.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}