docs(docs-infra): add version information element to the header

[ferrorenan]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit
• 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
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Currently we do not have the current version available in the header for easy and quick viewing, we only have it in the footer.

Issue Number: 51548

What is the new behavior?

Add a new element in the header informing the current version, to make it easier for the user to quickly and easily view the current version available.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[github-actions]

Deployed aio for 9746761 to: https://ng-dev-previews-fw--pr-angular-angular-51789-aio-l3cor0pe.web.app

Note: As new commits are pushed to this pull request, this link is updated after the preview is rebuilt.

[ferrorenan]

Hey @pkozlowski-opensource @JeanMeche

Do I need to do something else or just wait for approval?!

[H-dymitr]

@ferrorenan Hi, check commit message('version' is not an allowed scope.)

[ferrorenan]

@H-dymitr Yes, it's was wrong. I adjusted it, now just wait, thank you!

[ferrorenan]

Hey @AndrewKushnir

Could you take a look so we can see what's missing and finalize this PR?

[JeanMeche]

Hi, we're looking at deprecating angular.io in favor of https://angular.dev and suggestions shoud go toward the new site.

Feel free to drop any PR for improvements on the new doc site, thank you.

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