Investigate Large SyncTriggers Payloads

We're seeing failures in the Front End logs for a small percentage of customers where their SyncTriggers calls are being rejected due to the payload being too large. We need to investigate some of the customers with extremely large payloads to see what is pushing them over limit. There might be fixes we need to make in the construction of the payload to exclude some things.

To find some of the biggest offenders, runt the following Kusto query and look for the requests with the largest Cs_bytes:

AntaresIISLogFrontEndTable
| where PreciseTimeStamp >= ago(5h)
| where Cs_uri_stem == "/operations/settriggers"
| where Sc_status == 400
| order by Cs_bytes desc

We've made changes in ANT 84 to double the limit from 102400 bytes to 204800 bytes which satisfies the 95th percentile. Likely it is only error cases hitting the limit in these cases. We should investigate some apps and see what is causing the extremely large payloads. It might be:

- test_data being included in the payload. E.g. if the user has large test data files. Does the portal even need this data anymore? We could stop sending it
- too many secrets being sent (encrypted). e.g. perhaps in some cases there are a bunch of secrets backup files being sent along

See related PR https://github.com/Azure/azure-functions-host/pull/4676.