Allow Secrets to Create configuration

**Describe the problem you have/What new integration you would like**

Would it be possible to add a check to the "Create configuration" backend to allow for **Secrets** to be used?

For Example:

Currently, it results in plain text being added to the config:
```yaml
wifi:
ssid: "!secret ssid"
password: "!secret wifi_password"
```
- Note the included quotation marks.

Obviously, it needs to be:
```yaml
wifi:
ssid: !secret ssid
password: !secret wifi_password
```

**Please describe your use case for this integration and alternatives you've tried:**

It's obviously an advantage to use secrets in ESPHome and I think this feature could make the user experience smother.

**Additional context**

Thanks. 👍

Start by locating the Create configuration backend and tracing how values are serialized into YAML. Compare its output for ordinary strings with the requested !secret ssid and !secret wifi_password examples. Done means secret references are emitted without quotation marks and the generated configuration matches the examples.

Written by the indexing model from the issue text.