Workaround for the ParentOwner Limitation on Users (when a User is the parent of the content being created)
To make sure the User gets access to themselves when using (Parent)OwnerLimitation across 4.x and 5.x, the solution is to change the User to be the owner of their own Content item.
This is accomplished using a privileged user to do the following API calls: