feat(inputs): Add `[readonly]` property to input components

### Feature Description

Right now input components (checkbox, chips, datepicker, form field, radio button, select, slider) have `[disabled]` property. Only `matInput` directive has `[readonly]`.

`[disabled]` property conflicts with the `[formControl]` directive, which has a [property with the same name](https://github.com/angular/angular/blob/main/packages/forms/src/directives/reactive_directives/form_control_directive.ts#L72).

So if you use `[formControl]` with the components listed above, it is not possible to use their `[disabled]` property.

### Use Case

`[disabled]` controls [will not be included](https://github.com/angular/angular/blob/main/packages/forms/src/model/abstract_model.ts#L409) in `form.value` - sometimes you need to render an input element as read-only but still send its value to the server.

Start by comparing the existing [readonly] behavior on the matInput directive with the checkbox, chips, datepicker, form field, radio button, select, and slider components. Read the linked FormControlDirective property and AbstractControl documentation to understand the disabled/value interaction. Done means each listed component supports [readonly] without excluding its value from form.value.

Written by the indexing model from the issue text.