fix(@angular/cli): fix relative link to README not working on npm repo

[skander23000]

The link to the README was relative, which caused it to break when viewed on the npm repository. The link has been updated to an absolute URL to ensure it works properly.

Closes #29489

PR Checklist

Please check to confirm your PR fulfills the following requirements:

• [ x] 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)
• [ x] 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
• [x ] Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• [ x] No

Other information

[alan-agius4]

Thanks for your contribution.

[alan-agius4]

The changes were merged into the following branches: main, 19.1.x

[skander23000]

It doesn't fix the bug in the npm repo :( The link is not updated.
It is still pointing to '../../../README.md' instead of the correct one: 'https://github.com/angular/angular-cli/blob/main/README.md'.

Is the npm repo updated when the GitHub repo is? @alan-agius4

[andreas-aeschlimann]

As I mentioned in my issue, something weird is going on. The link never was relative on NPM, even though it was in Git.

I suspect that some script that we cannot see in the repo manipulates the URL before publishing to NPM.

[alan-agius4]

This still needs to be released on NPM.

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