Skip ignored hosts when checking existing config entries in config flow

[raman325]

Proposed change

There was a bug report that pointed out that when a vizio device has been ignored, config flow will fail because it expected the host key but the ignored config entry doesn't have it. This change only checks for expected keys when the config entry is not an ignored one. I wasn't sure how to test this, I found that the config component does a test like this by calling the WebSocket client to ignore an entry but that seemed messy. Happy to add tests if needed. If there's another hotfix version released for 0.108, it would be great to include this in that, otherwise it should go out with 0.109

Type of change

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

Additional information

• This PR fixes or closes issue: fixes Vizio TV won't integrate with Hass.io #33458

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

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

• Documentation added/updated for www.home-assistant.io

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

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

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

[MartinHjelmare]

Could we test this by adding a MockConfigEntry with source ignore and then starting the flow in the different entry points?

[raman325]

Thanks for that suggestion @MartinHjelmare was struggling to figure out how to test this, and by adding tests I found that my logic was flawed. Pushing a new commit shortly

[MartinHjelmare]

Looks good!