Investigate using "Append" AGO endpoint instead of ArcGIS "edit_features" function

[floptical]

It looks like we could see large performance improvements if we push directly to the '/append' AGO endpoint, instead of using the ArcGIS python module function "edit_features":

https://developers.arcgis.com/rest/services-reference/enterprise/append-feature-service-layer-.htm

This endpoint is supposedly higher performance. In fact in the ArcGIS code under the edit_features function it states:

When making large number (250+ records at once) of edits,
'append' should be used over 'edit_features' to improve
performance and ensure service stability.

It also would work much better with upserts, it provides the option 'upsertMatchingField' which allows us to choose a field as our primary key when upserting, instead of being forced to use the 'objectid', which requires us to first query AGO to determine.

We should investigate crafting an upsert to this endpoint and see how it works.