Enable strict template checks

[mark-drastrup]

Which issue does this PR close?

This PR closes #1985

What is the new behavior?

We will keep (and getting more strict) type checking our HTML files.

Does this PR introduce a breaking change?

• Yes
• No

Are there any additional context?

In the "describe the solution you'd like" section in the issue it says

Change the enum to a string union-type or a union of strings and the specific size/themecolor enums that already exist.
Beware of breaking changes in this regard.

This already seems to have been handled in #2099.

Checklist:

The following tasks should be carried out in sequence in order to follow the process of contributing correctly.

Reminders

• Make sure you have implemented tests following the guidelines in: "The good: Test".
• Make sure you have updated the cookbook with examples and showcases (for bug fixes, enhancements & new components).

Review

• Determine if your changes are a fix, feature or breaking-change, and add the matching label to your PR. If it is tooling, dependency updates or similar, add ignore-for-release.
• Do a self-review.
• Request that the changes are code-reviewed
• Request that the changes are UX reviewed (only necessary if your PR introduces visual changes)

When the pull request has been approved it will be merged to develop by Team Kirby.

[mark-drastrup]

I disabled strictDomEventTypes because it throws an error each time we try to access a property on a DOM event. Fx:

<input (change)="onChange($event.target.value)" />

All events are typed as a generic Event, which doesn't allow us to access $event.detail.checked or $event.target.value, which we do in many components. I did initially handle it by passing the event to the method and do the typing in there. That solution was a bit cumbersome, especially when doing it for Ionic events, that needs to be handled like this:

import { ItemReorderEventDetail } from '@ionic/angular';

doReorder(event: Event) {
  const customEvent = event as CustomEvent<ItemReorderEventDetail>;
  // replace event usages with customEvent
}

Since we have to type cast the event in the method, I think we lose the value of type checking the input in the template.

[kodeaben]

In the issue, Rasmus wrote " be aware of brekaing changes" did you nit find any?

[mictro]

Not optimal - but good enough :)

[mictro]

Goood...