Collection transaction operations

[emmanuelmathot]

Related Issue(s):

• Collection PATCH operation #5: PATCH Collection operation

Proposed Changes:

1. Add the PATCH /collections/{collectionsId} operation to the extension
2. Add the patchCollection schema to specify the fields of the collection that can be updated
3. Add the DELETE /collections/{collectionsId} operation to the extension

PR Checklist:

• This PR has no breaking changes.
• I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.

[philvarner]

1. I think we should move this into a separate Collections Transaction extensions, since this spec is based on the OGC Part 4 spec and is Candidate/Stable maturity. Collections txn should have a different conformance class anyway, and I think it makes sense to split them into two different specs that can mature at different rates.
2. POST for create and PUT should also be supported, not just PATCH and DELETE.
3. Maybe for DELETE, there needs to be a way to specify recursive or non-recursive delete.