Add tile card feature for input_select domain

[rbnis]

Proposed change

This PR adds the option to select an option of an input_select entity.
With this users have an easy way to integrate input_selects into their dashboards.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

The feature in this PR does not need any additional configuration.
But to test this feature I added an input_select entity with the id input_select.demo and name Demo.
This input_select has the options foo, bar, baz and qux.
Then I added a dashboard with this configuration:

views:
  - title: Home
    cards:
      - type: tile
        entity: input_select.demo
        features:
          - type: input_select-options
            options:
              - foo
              - baz
              - qux

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.
  • Im not sure what tests to add for the changes in this PR. If this is needed any guidance is appreciated :)

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io
  • I have only prepared a branch with the documentation change but have not yet opened a PR as I have a question regarding the coordination of publishing the docs and releaseing the feature.
    • Is it enough to just link from the docs PR to this PR? Or do I have to do anything else?

[home-assistant]

Hi @rbnis

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[spacegaier]

Could you add a screenshot to show how it would look like?

[piitaya]

Hi 👋
Thanks for the contribution.
There are some missing points before merging it :

• Select entities must be supported too
• If there are many options, the texts will not fit. You should display a dropdown (but we didn't have one that fit the tile card for now 😔). And we can add an option list | dropdown so the user can select the desired display.

[piitaya]

Can we rename it to select-options and add support for select entity too?

[piitaya]

Suggested change

	(localize: LocalizeFunc, stateObj?: HassEntity) =>
	(stateObj?: HassEntity) =>

[piitaya]

Suggested change

	`ui.panel.lovelace.editor.card.tile.features.types.alarm-modes.${schema.name}`
	`ui.panel.lovelace.editor.card.tile.features.types.select-options.${schema.name}`

[piitaya]

Should support select entities too.

[piitaya]

Suggested change

	(option) =>
	this._config?.options?.includes(option) ||
	this._config?.options === undefined ||
	this._config?.options?.length === 0
	)
	(option) =>
	this._config?.options?.includes(option) ||
	this._config?.options === undefined
	)

If options is empty we must display nothing.

[piitaya]

This must be a label, not options

[piitaya]

I close this PR as it's replaced by #17971.