Vonage

- Adding support for the [Vonage Meetings API](https://developer.vonage.com/en/meetings/overview)
- Adding partial support for the [Vonage Proactive Connect API](https://developer.vonage.com/en/proactive-connect/overview) - supporting API methods relating to `lists`, `items` and `events`
- Returning a more descriptive (non-internal) error message if invalid values are provided for `application_id` and/or `private_key` when instantiating a Vonage client object

- Adding support for the [Vonage Subaccounts API](https://developer.vonage.com/en/account/subaccounts/overview). - The subaccounts API is disabled on accounts by default. If you want to use subaccounts, [contact support](https://api.support.vonage.com) to have the API enabled on your account.

- Using the [Vonage JWT Generator](https://github.com/Vonage/vonage-python-jwt) instead of `PyJWT` for generating JWTs.
- Other internal refactoring and enhancements

- Updating the internal use of the `fraud_check` parameter in the Vonage Verify V2 API

- Adding support for V2 of the Vonage Verify API
- Multiple authentication channels are supported (sms, voice, email, whatsapp, whatsapp interactive messages and silent authentication)
- Using fallback channels is now possible in case verification methods fail
- You can now customise the verification code that is sent, or even specify your own custom code
- Adding `advancedMachineDetection` functionality to the NCCO builder for the Vonage Voice API

- Internal refactoring changes
- Using header authentication for the Numbers API