Make it possible to set options and system options on entry create

[scop]

Description:

Make it possible to create config entries with an initial set of options and system options. This is especially useful on config import, and for some integrations it would be desirable to disable new entities by default as discussed in #26675.

Related issue (if applicable): #26675, #27612 (alternative approach)

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the [development checklist][dev-checklist]

[scop]

Not sure if passing through kwargs as is in FlowHandler.async_create_entry is desirable like done here, or of we should override async_create_entry in ConfigFlow and add explicit options and system_options handling there instead. No strong opinions, opted for the former because it's less code :P

[balloob]

I am not a fan because it feels weird. Data should be the data for the config entry, all other is metadata about the step.

Not sure what the correct thing is .

[scop]

Whatever way that makes it possible to set disable_new_entities to True for a newly created config entry works for me. I wouldn't want to handle disabling the entities manually, and it would be weird if the UI shows new entities being enabled by default where in fact they are created disabled.

Anyway, not sure I understand your concern, but I do think this (options and system_options) is stuff about the config entry, it's not a step thing. It gets persistent with the config entry, UI shows the new entity enablement toggle for the entry, etc.

Or maybe you're concerned about opening the big kwargs possibility to data_entry_flow? As mentioned, that could be left alone and replaced by doing this in ConfigFlow just for options and system_options.

[scop]

Alternative approach: #27612

[scop]

Withdrawing due to concerns, and #26675 uses a different/selective approach now.