Fix deconz allow_clip_sensor and allow_deconz_groups options

[Anonym-tsk]

Description:

I found that options allow_clip_sensor and allow_deconz_groups in core.config_entries don't work.
It started from PR and async_populate_options function that moved these values from config_entry.data to config_entry.options.
According to this comment there is no way to change this options via UI.
But now they works and i can change them in core.config_entries.

Related issue (if applicable): fixes #

Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>

Example entry for configuration.yaml (if applicable):

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

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

• Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[probot-home-assistant]

Hey there @Kane610, mind taking a look at this pull request as its been labeled with a integration (deconz) you are listed as a codeowner for? Thanks!

[Kane610]

How could I have missed this? Thanks!

[Anonym-tsk]

@Kane610 @balloob Please merge this PR to master if it's possible

[Kane610]

Thanks for fixing this!