Improve on extended diagnostics for signal invocation

[undsoft]

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

No response

Description

#49657 ensures that signals are called in situations like:

{{ mySignal }}

However, there are other cases where it's easy to make a mistake, especially when migrating from old @Inputs.
The following cases produce no warnings:

<div *ngIf="mySignal"></div>
<div [class.red]="mySignal"></div>
<div [attr.data-something]="mySignal"></div>
<input [disabled]="mySignal">

While it's possible to write code where statements above are valid, I would argue that it's likely a mistake and that compiler should warn about those cases.
If we don't want to add this functionality to Angular, I can create a ticket in angular-eslint.

Proposed solution

Extended diagnostics should warn when signals are not called in additional scenarios.

Alternatives considered

Creating this ticket in angular-eslint repo :)

[eneajaho]

Related #54324

[devversion]

We improved this, as per link of @eneajaho. In addition, I have a some backburner work to enable type checking for DOM properties as well. This would catch issues like this even without the extended diagnostic.

Keeping this open to track the root problem: DOM type checking not enabled by default.