dotCMS CLI: Implement files push command

[nollymar]

Parent Issue

#24732

User Story

As a user, I'd like to execute the files push command to upload file(s) or/and folder(s) from my local machine to a remote server (dotCMS) by specifying the location of the local directory or file.

Examples:

files push /cli/project/workspace/path --dry-run
files push /cli/project/workspace/path
files push /cli/project/workspace/path/files/live/es-es/demo.dotcms.com
files push /cli/project/workspace/path/files/live/en-us/demo.dotcms.com/images
files push /cli/project/workspace/path/files/live/en-us/demo.dotcms.com/images --dry-run
files push /cli/project/workspace/path/files/live/en-us/demo.dotcms.com/application/themes/landing-page/header.vtl

This command should consume the endpoint implemented here: #24738

Acceptance Criteria

• The "push" operation should allow the user to upload file(s) or/and folder(s) from their local machine to dotCMS.
• The user should be able to preview changes that would be made on the remote server without applying them through the "--dry-run" option.
• The "push" operation should display appropriate progress messages as the file(s) or/and folder(s) are uploaded.
• If a file is archived, we should unarchive/publish it
• Make sure zero length files can be pushed. Related to Error when update zero size file through Webdav or CLI. #24042
• Implement tests accordingly

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

[dcolina]

Note: I have noticed that some actions have changed in definition, so it would be good to update the user history to avoid confusion.

This can be checked by looking at the result of the. files push --help command

Otherwise, the task meets each of the requirements specified in the acceptance criteria.

Test cases:

Push a new file

Given:

A new image file on working status and es-es lang, in this case we add kunisports-1.jpg.

When:

Run files push command.

Then you can see the new file pushed and in draft status.

![Image](https://github.com/dotCMS/core/assets/29883881/bd044c59-1ced-441d-a473-037b656d758b

Push file with dry-run option

Given:

A new folder and a new file in it on live status and en-us lang, in this case we add nested-folder/jijantes-fc.svg

When:

Run files push --dry-run command.

Then:

You can see the new folder and the new file in the projection.

Push an empty folder

Given:

A new folder (empty) in it on live status and en-us lang, in this case we add nested-folder/

When:

Run files push command.

Remove a folder and its content

Given:

Remove the event folder and its content on live status and en-us lang, in this case events

When:

Run files push --removeAssets command.

Push with empty-file (zero bytes)

Given:

A new empty file (zero bytes).

When:

Run files push

Then:

Push with empty-folder

Given:

A new empty folder.

When:

Run files push

Then:

The empty folder is ignored.

Remove folders and assets

Given:

Delete an existing folder and its all content.

When:

Run files push --removeAssets --removeFolders command.

Then:

You can see the folder new-folder and its content have been disappeared.

Fail fast option

Given:

• Add a image file. In this case we added kunisports-1.jpg
• Add some files to force errors. In this case we added unsupported files like .json or .svg files.

When:

Run files push --fail-fast command.

Then:

Now we removed the file with errors.

When:

Run files push --fail-fast command again.

Then:

Successfully execution, this means the command is working fine.

Internal QA: PASSED.