Add verbose flag to the "bundle deploy" command

[ilia-db]

Changes

• Extract sync output logic from cmd/sync into lib/sync
• Add hidden verbose flag to the bundle deploy command, it's false by default and hidden from the --help output
• Pass output handler to the deploy/files/upload mutator if the verbose option is true

The was an idea to use in-place output overriding each past file sync event in the output, bit that wont work for the extension, since it doesn't display deploy logs in the terminal.

Example output:

~/tmp/defpy: ~/cli/cli bundle deploy --sync-progress
Building defpy...
Uploading defpy-0.0.1+20240917.112755-py3-none-any.whl...
Uploading bundle files to /Users/ilia.babanov@databricks.com/.bundle/defpy/dev/files...
Action: PUT: requirements-dev.txt, resources/defpy_pipeline.yml, pytest.ini, src/defpy/main.py, src/defpy/__init__.py, src/dlt_pipeline.ipynb, tests/main_test.py, src/notebook.ipynb, setup.py, resources/defpy_job.yml, .vscode/extensions.json, .vscode/settings.json, fixtures/.gitkeep, .vscode/__builtins__.pyi, README.md, .gitignore, databricks.yml
Uploaded tests
Uploaded resources
Uploaded fixtures
Uploaded .vscode
Uploaded src/defpy
Uploaded requirements-dev.txt
Uploaded .gitignore
Uploaded fixtures/.gitkeep
Uploaded src/defpy/__init__.py
Uploaded databricks.yml
Uploaded README.md
Uploaded setup.py
Uploaded .vscode/__builtins__.pyi
Uploaded .vscode/extensions.json
Uploaded src/dlt_pipeline.ipynb
Uploaded .vscode/settings.json
Uploaded resources/defpy_job.yml
Uploaded pytest.ini
Uploaded src/defpy/main.py
Uploaded tests/main_test.py
Uploaded resources/defpy_pipeline.yml
Uploaded src/notebook.ipynb
Initial Sync Complete
Deploying resources...
Updating deployment state...
Deployment complete!

Output example in the extension:

Tests

Manually for the sync and bundle deploy commands + vscode extension sync and deploy flows

[pietern]

Please move the outputWaitGroup below with its own comment.

The sync type didn't spawn its own routine before, and it was possible to call Events(), then RunOnce(), then Close(), and repeat. This is no longer possible now that we construct the events channel from the constructor. I suspect calling Events() will actually be problematic now.

[ilia-db]

Removed the Events completely, as it's not used now

[pietern]

I see how this is necessary in the current setup (where we have no good means to pass this information from both the sync command and the deploy command). In some future we'll want to decouple this again and deal with output from the caller, passing only the channel with events.

[ilia-db]

True, although output handler accepts a channel with events and it's set by the caller, so the caller is in control on how to deal with events. We can turn things around and create events channel on the caller side, passing it to the sync logic, not sure if there are any practical benefits of that