consider simplifiying dependency chain

[mnoreen]

Issue Summary

This is a request. Please consider simplifying (perhaps by replacing) the dependency on Microsoft Identity. The dependency chain for the Twilio library is getting out of hand, largely due to the Microsoft IdentityModel Tokens dependency itself. It adds 14 packages alone! And it also adds a rather significant chunk of "bindingRedirect" code to app.config.

For one project, that might not seem a big deal. But... we have many specialized console apps and several distinct websites. This proliferation (clutter!) is a lot to carry around and keep track of and discern if it's "really necessary." We don't blindly just accept whatever comes down from a nuget update, we try to keep a solid grasp of what underlying tech is involved. This is now becoming just too much.

Is there a more streamlined authentication layer you can use other than Microsoft's Identiy Model (which seems to have turned into an ugly beast...)?

Steps to Reproduce

1. Start a new console app (c#, .NET Framework 4.8)
2. Use nuget to add Twilio and it's initial dependencies (including one on Microsoft.IdentityModel.Tokens)
3. Use nuget to update packages. Now the list of dependencies is significantly longer than it was before!

[sbansla]

Hi @mnoreen
We will be checking the issue.