Adding app deploy command

[sfc-gh-gbloom]

Pre-review checklist

• I've confirmed that instructions included in README.md are still correct after my changes in the codebase.
• I've added or updated automated unit tests to verify correctness of my new code.
• I've added or updated integration tests to verify correctness of my new code.
• I've confirmed that my changes are working by executing CLI's commands manually.
• I've confirmed that my changes are up-to-date with the target branch.
• I've described my changes in the release notes.
• I've described my changes in the section below.

Changes description

Adding the snow app deoply command, which syncs the local changes to the stage without creating/updating the application (More details in SNOW-1215781).

Since the deploy command is basically the same as the run command without the last step of creating/updating the application, the most minimal change would be to add a flag to skip this step in the existing NativeAppRunProcessor class.

An alternative approach would be to add a dedicated DeployProcessor and refactor the common code up to the base class.

The next step will be to extend the command to accept optional file paths arguments to sync only specific files: snow app deploy [file]*.

Test

Created a basic app:

snow app run -c QA3 --warehouse TEST1

Running deploy with no changes:

snow app deploy -c QA3

There are no new files that exist only in your local directory.
There are no new files that exist only on the stage.
There are no existing files that have been modified, or their status is unknown.
Existing files identical to the stage:
README.md
manifest.yml
setup_script.sql

Making a change to the readme and running deploy again:

snow app deploy -c QA3

Existing files modified or status unknown:
README.md
Existing files identical to the stage:
manifest.yml
setup_script.sql
Uploading diff-ed files from your local /Users/gbloom/gbloom-training-app/output/deploy directory to the Snowflake stage.

[sfc-gh-bgoel]

IMO, we should do the alternative suggested in the description, i.e. to have a dedicated DeployProcessor class which will handle bundle, package creation and upload to stage without any application creation. This allows for single responsibility to be followed, in this case the ecosystem involved in app package creation.
I understand that the way this is done right now is to introduce minimal changes, perhaps as a poc. But we should refactor this properly if we are to make changes to the main branch.

[sfc-gh-bdufour]

Approach LGTM, other than the one comment I have on this draft.

[sfc-gh-gbloom]

Closing this in favor of #921