Transition Duo Watcher to pull logs from "v2" endpoints

[chmc3]

Duo now supports a "v2" endpoint with additional logging from the Authentication and Telephony logs.
https://duo.com/docs/adminapi#authentication-logs

GET or POST /admin/v2/logs/authentication
GET /admin/v2/logs/telephony

Because the responses will change, and systems rely on the Duo Watcher logs, it is inadvisable that we simply update all calls to the new methods. Instead, a new integration will be set up that will allow us to test the new endpoints and allow us to transition functions to utilize the new logs.

• Evaluate the documentation at https://duo.com/docs/adminapi#logs to determine where value can be gained from the new logs (https://duo.com/docs/adminapi#authentication-logs and https://duo.com/docs/adminapi#telephony-logs)
• Configure a new application in Duo for Admin Log reading
• Identify high value applications/functions that rely on Duo Watcher
• Transition applications/functions/downstream consumers to use v2 logs

[chmc3]

New application created in Duo for "UW-IT Duo Watcher test" to allow testing of v2 calls, and can be used to transition if needed.
Application key ends in 6EJS and Secret Key ends in Mwak