V1 REST API (GET /nodes/{nodeId}/children) returns working copies when files were offline edited in Share and may cause irrevocable damages and confusion

[Step to reproduce]
1. In Share, "edit offline" a document.
2. In ADW or a custom UI that talks to the new V1 Rest API, list children of the folder where the document is in.

[Actual Result]

When a document is being edited offline in Share, you will see two documents in ADW, one of them is the working copy.

However, in reverse, when you edit offline a document in ADW, you won't see a working copy (as it only locks it) so the behavior is inconsistent across the apps.

[Expected Result]

The customer is requesting Alfresco to add a filter to the existing list of filters in the v1 rest API (GET /nodes/{nodeId}/children) so that ADW/custom UIs can simply filter out Working Copies if they don't want to see them and get a seemless experience and not run into problems across the two UIs.

The customer is not using ADW but their own Angular app that talks to the V1 REST API and is hoping to have a filter to remove working copies when listing children. I am just using ADW to demonstrate the issue.

[Problems]

The problem with displaying working copies via "/nodes/{nodeId}/children" is that customer can carry out actions on the working copies accidentally and cause irrevocable damages and confusions.