updating all APi 1.x endpoints to 2.0 for compatibility

[ragen14]

What does this PR (Pull Request) do?

• This PR fixes Ansible playbooks still use Traffic Ops API v1 #5377 OR is not related to any Issue

Which Traffic Control components are affected by this PR?

• Ansible Infrastructure code

What is the best way to verify this PR?

Best way to verify the change is to build CDN infra using the Ansible playbook in infrastructure/ dir

If this is a bug fix, what versions of Traffic Control are affected?

The following criteria are ALL met by this PR

• This PR includes tests OR I have explained why tests are unnecessary
• This PR includes documentation OR I have explained why documentation is unnecessary
• This PR includes an update to CHANGELOG.md OR such an update is not necessary
• This PR includes any and all required license headers
• This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Additional Information

[zrhoffman]

GET /cdns/{{name}}/snapshot/new still uses API v1:

trafficcontrol/infrastructure/ansible/roles/to_api/tasks/snapshot.yml

Line 67 in 2ba34d6

url: "{{ to_api_base_url }}/api/1.2/cdns/{{ to_api_target_cdn }}/snapshot/new"

[ragen14]

woops!!.. done

[zrhoffman]

https://github.com/apache/trafficcontrol/blob/f68d06801126b857e23fd943fd58bfc5eb81abfa/infrastructure/ansible/roles/dataset_loader/tasks/ds_loader.yml#L125-L126

needs to be /cdns/name/{{ Target_cdn_name }}/sslkeys.json without .json.

[zrhoffman]

Changes look good but the PR still needs to be tested.

[zrhoffman]

• API version is changed to 2.0 on all TO endpoints
• API v1-only endpoints are changed to their API v2 equivalents

Testing confirms that it works!

[zrhoffman]

There is a changelog merge conflict from #6073.