Config entry selectors don't fully handle entries without a title

[dougiteixeira]

Checklist

• [X] I have updated to the latest available Home Assistant version.
• [X] I have cleared the cache of my browser.
• [X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

The configuration entry selectors were designed for when the entry has no title, displaying the message "Unnamed entry", however when selecting an entry without a title the field is not filled with anything visible.

See an example:

https://github.com/home-assistant/frontend/assets/31328123/51d71875-2e8d-4412-9200-9061e898c29e

The user can remove the title of the integration's config entry through the UI.

Describe the behavior you expected

That when selecting a config entry without the title, the translated domain of the integration or even the ID of the config entry would be displayed.

On this topic I have some behavior suggestions:

• When the config entry does not have a title, the name of the integration is shown as primary information and the message "Unnamed entry" as secondary information in the selection list.

• When the config entry has a title continue with the current behavior: show the title of the config entry as primary information and the integration name as secondary information in the selection list.

• When selecting a config entry that does not have a title, the name of the integration is displayed in the field.

Steps to reproduce the issue

1. Remove the title of the integration configuration entry via the Rename floating menu on the integration page.
2. Access any blueprint that makes use of the config entry selector and select the config entry that has been untitled.

What version of Home Assistant Core has the issue?

2024.7.2

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response