Partner Support user can resolve Disapproved Ads without relying on viewing AdWords UI

Success Criteria:
1. If Google rejects an ad upon deployment, there is an alert sent out within 24 hours (extending AML+Admin Problems Alert sent to AML-OPs for Ad Extension issues delivered in Wickford. AML Subscriber stack identifier required (nice to have include Merchant UUID)

2. If Google rejects an ad post deployment, it is logged and combined with all the information necessary (see below) to identify the specific ad in the AML UI and reason for rejection.

3. All rejected ads and relevant information are available for a TSA non-developer power user (e.g. Kishor) to access daily. (This may turn into a process where TSA-India grabs a file off of a production server for each subscriber and sends out to Partner Support and Editorial team as needed.)

As a result of the above, Partner Support user can review the information and determine if TSA Editorial needs to resolve (for system generated content) or forward relevant information to the Subscriber to resolve (for custom content).

The information required for each disapproved ad are:
Subscriber Name or AML instance #
Merchant UUID
BA+Loc Campaign (taxonomy names)
Campaign Name
Ad group Name
Ad Copy Headline, D1, D2, both URLs
Offending text
Reason Codes
System v. Custom flag (this is at the ad level)

This replaces AML-2350 and AML-1884