integration test: latest V2 with legacy policies -> force-upgrade to latest V2 with legacy policies

[bcmdarroch]

adds 1 integration test script that runs the following scenario:

1. start on the Automate build just before the force-upgrade-IAMv2 build, set to IAM v2
2. take a database screenshot
3. upgrade Automate to the latest build with force-upgrade-IAMv2
4. run 3 inspec controls:
   • a new a2-iam-integration-legacy control that tests IAM specific behavior:
     - verify that all v1 default policies, v1 custom policies, v2 chef-managed, v2 custom policies were migrated and are enforced
     - editor and viewer teams persist and have their most up-to-date names
     - some IAM-specific controls ported from a2-iam-v2-*tests
   • a2-api-smoke control that has been updated to all v2 API paths
   • a2-api-integration that now only tests v2 API behavior (this should involve porting tests from a2-iam-v2-* and then removing those controls)
5. confirm database has all the data we expect (maybe covered by inspec tests?)

NOTE: a2-iam-integration tests should focus on testing different levels of permissions on APIs, whilea2-api-integration tests should assume the subject is allowed to exercise the API and should focus on actual API behavior