API Acceptance test steps for flexible share creation

[phil-davis]

PR #32699 added the ability to directly create a public link share with expiry date.
Existing test steps can create shares with various permissions.
It would also be useful to have:

• steps for directly creating an ordinary share with expiry date
• steps for more general creation of an ordinary and a public link share where you can specify a table of share attributes, so you can mix permissions, expiry date, share recipient etc.

[phil-davis]

Note: in Sharing.php we have userCreatesAShareWithSettings($user, $body)
That lets you specify a table of settings.
Its downside is that to get a public share you have to put in the table:

| shareType | 3           |

The "magic" numbers for share types make for test scenarios that are not so readable.

So, when sorting all this out, consider how to have steps that are a combination of "totally flexible" vs "readable".

[ownclouders]

GitMate.io thinks the contributor most likely able to help you is @PVince81.

Possibly related issues are #22485 (test), #22492 (test), #31579 (test), #31516 (Acceptance test coding standard changes), and #31696 (Acceptance tests for exclude users from sharing changes).