Possibly change feature add, update and delete params to match REST API at some point

[COV-GIS]

It's personal preference but adds, updates and deletes params really bother me for not being the REST params, e.g. features and objectIds respectively. I never fully understood the JS API having different param names from the REST API for queries and the like. I get it, outSpatialReference is more descriptive than outSR, but the rest of the param names here are REST API driven. I just like being able to look at the REST API docs and know I can pass any param as is.

I thought about it at the time the functions were added but didn't mention it. This would be a breaking change. So may never happen. But if there ever is a v2 candidate or other opening to change the param names I'd be happy to submit changes.

[jgravois]

we actually already discussed this in Esri/hub.js#58 (and #137)

a PR that introduces features and objectIds and adds a deprecation warning when parsing what we already have would be most welcome.

[COV-GIS]

I'm not the only one then.

Will do.

[COV-GIS]

#396