Add info-level extended diagnostics

[haqer1]

Which @angular/* package(s) are relevant/related to the feature request?

compiler-cli

Description

There could be defaulted compilation behavior that doesn't fall into error or warning categories, whereas still deserving a message.

One example potentially being what is suggested in #56305

Proposed solution

Info-level extended diagnostic message support.

P.S.
That seems natural in the long run sooner or later...

Alternatives considered

NA

[haqer1]

Just thinking out loud.
Could (some) *ngIf (or @if) conditionals possibly constitute another example of this?
For instance:

1. https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Statements/if...else

const b = new Boolean(false);
if (b) {
  console.log("b est équivalent à vrai"); // "b est équivalent à vrai"
}

In TS:

<a routerLink="async-promise-pipe" *ngIf="tf">with promise</a>
...
tf: Boolean = new Boolean(false);

2. Assignment in conditional (personally, i make such shortcuts in all languages from time to time (but usually not assigning true)):

if (this.tf = true)
/**/;

JS example: https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Statements/if...else
3) Or perhaps even more common: conditionals not evaluating to true but getting converted [including 1) in particular]...

[JeanMeche]

What would be the value of info instead of a warning ? Warnings are non-blocking reportings which info would also be.

[haqer1]

Less severe: especially for the case in the OP, where conclusion seems non-problematic. Warnings usually are probably more problematic. Infos like this could simply be let go (until one has the time to care).

[haqer1]

Another dimension is automatism:
when the conclusion made is likely error-proof, like in the OP, the call could be compiled by default, w/ message being just for info (at info or warning level).

P.S. Warnings at present always require manual action (perhaps also reflecting the fact there is less certainty there?).