Publishes batches of changes grouped by repository. Send an array of
repository objects, each with at most 20 testEntities. Use an explicit
testProjectId to avoid selecting or creating the default Cloud repository.

Supported combinations in this reference:

• TEST_CASE: CREATE, UPDATE, RENAME, MOVE, DUPLICATE, DELETE.
• TEST_SUITE: CREATE, UPDATE, ADD_TEST_CASES, RENAME, MOVE, DUPLICATE, DELETE.
• TEST_FOLDER: CREATE, RENAME, MOVE, DUPLICATE, DELETE.

For test cases, create/duplicate require TestCase:Create, update/rename/move
require TestCase:Update, and delete requires TestCase:Delete. Suites use
the corresponding TestSuite permissions; adding members requires
TestSuite:Update. Folders use the permissions of their type.

CREATE needs a name for a case or suite; supply its parent folder path.
A blank case path defaults to Test Cases. New cases default to status
PUBLISHED and priority MEDIUM; manual cases default to automation
status TO_BE_ASSESSED.
Folder CREATE takes the complete new folder path and testFolderType.
Other actions identify the existing asset with data.id. RENAME
takes the new name. Case/suite MOVE takes the destination parent path;
folder MOVE takes the complete destination folder path, including its name.
DELETE needs only the existing ID and can affect linked assets.

Case UPDATE changes supplied fields; omitted manual content is preserved.
Suite UPDATE requires a membership list and replaces membership with it;
send testSuiteItems containing the complete
desired list, or [] to remove all members. It does not rename the suite.
Use ADD_TEST_CASES to add members without replacing the existing list.
testCaseIds is the older, version-unaware alternative.

Folder rename, move, and delete affect descendants. Suite-folder changes
other than creation require an eligible Cloud repository and the feature
enabled for your organization; the root Test Suites folder cannot change.
A deleted suite can remain available as historical uploaded execution data.

With async=false, returned entity data includes created IDs. With
async=true, the response can contain a task rather than completed changes.
Even a synchronous response can include workspace or publication task data;
do not treat it as proof that repository files have finished publishing.