New Registry API capability: new filter operator, merge mode, group operations and more

[t83714]

New Registry API capability: new filter operator, merge mode, group operations and more

To help the access group feature development, we need the following enhancement:

• add :<| & :!<| operator (item in array) to regsitry api get records api
  • See API Doc (Test Server Might not always be available, if not please build doc from the branch)
• add {patch} /v0/registry/records API: Modify a list of records by applying the same JSON patch on specified aspect
  • See API Doc
• add merge switch to {put} /v0/registry/records/{recordId}/aspects/{aspectId} Modify a record aspect by ID API
  • when merge query parameter = trure, the supplied new aspect data will be merged into existing aspect data (if exists).
  • If no existing aspect data can be found, no error will thrown and the aspect will be created.
  • array items will be merged with no duplication. See test case here
  • API Doc
• add API {put} /v0/registry/records/aspects/:aspectId Modify a list of records's aspect with same new data
  • API Doc
• add API {delete} /v0/registry/records/aspectArrayItems/:aspectId Remove items from array of aspect data of a list of records
  • this API goes through the aspect data that is specified by aspectId of a list of registry records and delete items from the array that is located by the jsonPath.
  • If the aspect doesn't exist for a record or the array can't be located with the jsonPath string or the value located with the jsonPath string is null, the operation will be skipped without throwing an error.
    • 0 will be returned as eventId (operation result eventId) for this case.
  • If the JSON data that is located by the jsonPath string exists and is not an Array or null, an error will be thrown and 400 code will be responded.
  • API Doc

Relevant PR: #3365

[t83714]

the changes are done and available in the dev cluster --- the ticket was created to link all relevant info (API docs, code) together. So when people need it, can find it easily.
The ticket will be closed after I completed & fully tested PR: #3365

[t83714]

closed via PR: #3365