Migrate twilio webhooks to the webhook component

[rohankapoorcom]

Description:

Migrating Twilio over to the webhook API so that it doesn't need an api password.

This is built on top of #17464 (which needs to be merged before this one). Tests will not pass until after that is merged.

Breaking Change: Each instance of Home Assistant will now generate it's own unique webhook url for Twilio to use. One will need to be generated and provided to Twilio for incoming calls/messages from Twilio to Home Assistant to continue to flow.

I followed the approach used in #16817 to implement a new config flow to register the webhook. Existing configuration (account_sid, auth_token) still occurs via the configuration.yaml file.

I do not actually use twilio myself so I cannot test the behavior with Twilio, but the unit tests look okay.

Related issue (if applicable): Related to #15376

Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#7074

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass

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:

• New dependencies have been added to the REQUIREMENTS variable (example).
• New dependencies are only imported inside functions that use them (example).
• New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

If the code does not interact with devices:

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

[houndci-bot]

blank line at end of file

[houndci-bot]

blank line at end of file

[balloob]

I rebased but it didn't pass tests.

[rohankapoorcom]

Now that I think about it, we probably don't want to support the webhook id being set by the yaml config...

[rohankapoorcom]

Very strange, I'm able to reproduce locally, the error it's showing is ModuleNotFoundError: No module named 'twilio'. This is provided within the REQUIREMENTS for twilio as well as within requirements_all.txt

Any idea why it wouldn't be finding the module?

What's even more confusing is that it works fine when running Home Assistant and does in fact install the twilio module and the component loads correctly.

[balloob]

twilio needs to be part of the test requirements. Open gen_requirements.py and add twilio to the list.

[balloob]

Or better, don't add it to the list and mock it using MockDependency

[houndci-bot]

'unittest.mock.Mock' imported but unused

[rohankapoorcom]

@balloob @MartinHjelmare does this need a breaking change label? The breaking change paragraph is in the description.

[balloob]

Added!