### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

Hello,
not sure if this is an actual issue or just me misunderstanding behaviour of structural directives in Angular.

Let's say we have a simple structural directive (see [repro](https://stackblitz.com/edit/angular-ivy-vbzbnj?file=src%2Fapp%2Funless.directive.ts,src%2Fapp%2Fapp.component.html,tsconfig.json,src%2Fapp%2Fapp.module.ts,src%2Fapp%2Fapp.component.ts)). From my point of view, two declarations below should be equal, however, the first one throws type error, while the second one compiles without any errors. Why is that?

```ts

Test

Test

```

From my point of view, typechecker expects the structural directive without any parameters to be equal to following:

```ts

Test

````

when in reality, it is equal to code above (I tried to change the type of the directive parameter to `boolean | string`, and checked if the input setter will be called - it wasn't).

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-ivy-vbzbnj?file=src%2Fapp%2Funless.directive.ts,src%2Fapp%2Fapp.component.html,tsconfig.json,src%2Fapp%2Fapp.module.ts,src%2Fapp%2Fapp.component.ts

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

_No response_

### Anything else?

_No response_

Start with the StackBlitz reproduction, especially src/app/unless.directive.ts, src/app/app.component.html, tsconfig.json, src/app/app.module.ts, and src/app/app.component.ts. Reproduce the differing type-checking behavior for *appUnless and the equivalent ng-template form, then trace Angular's structural-directive template checking. Done means the behavior is explained and the two forms are handled consistently if the reported behavior is confirmed.

Written by the indexing model from the issue text.