Rsconnect-python

Added
- The `CONNECT_REQUEST_TIMEOUT` environment variable, which configures the request timeout for all blocking HTTP and HTTPS operations. This value translates into seconds (e.g., `CONNECT_REQUEST_TIMEOUT=60` is equivalent to 60 seconds.) By default, this value is 300.

Fixed

- Extra files were not being included in deploy Voila.

- Error message to indicate the Python also has to be configured in Connect.

Added
- Added `deploy voila` command to deploy Jupyter Voila notebooks. See the [user documentation](https://docs.posit.co/connect/user/publishing-cli-notebook/#interactive-voila-deployment)
for more information.

Changed
- `deploy html` was refactored. Its behavior is described below.

Deploying HTML
Specifying a directory in the path will result in that entire directory*, subdirectories, and sub contents included in the deploy bundle. The entire directory is included whether or not an entrypoint was supplied


e.g.
using the following directory,

├─ my_project/
│ ├─ index.html
│ ├─ second.html

and the following command:

rsconnect deploy html -n local my_project

or this command:

rsconnect deploy html -n local my_project -e my_project/index.html

we will have a bundle which includes both `index.html` and `second.html`

- specifying a file in the path will result in that file* - not the entire directory - included in the deploy bundle

e.g.
using the following directory,

├─ my_project/
│ ├─ index.html
│ ├─ second.html

and the following command:

rsconnect deploy html -n local my_project/second.html

we will have a bundle which includes `second.html`

- a note regarding entrypiont
- providing an entrypoint is optional if there's an `index.html` inside the project directory, or if there's a *single* html file in the project directory.
- if there are multiple html files in the project directory and it contains no `index.html`, we will get an exception when deploying that directory unless an entrypoint is specified.

- if we want to specify an entrypint, and we are executing the deploy command outside a project folder, we must specify the full path of the entrypoint:


rsconnect deploy html -n local my_project -e my_project/second.html


- if we want to specify an entrypint, and we are executing the deploy command inside the project folder, we can abbreviate the entrypoint, like so:

cd my_project
rsconnect deploy html -n local ./ -e second.html



*Plus the manifest & other necessary files needed for the bundle to work on Connect.

Fixed

- Extra files were not being included in certain deploy and write-manifest commands.

Added

- The `--cacert` option now supports certificate files encoded in the Distinguished Encoding Rules (DER) binary format. Certificate files with DER encoding must end in a `.cer` or `.der` suffix.
- The `--python` option now provides additional user guidance when an invalid path is provided.

Changed

- The `--cacert` option now requires that Privacy Enhanced Mail (PEM) formatted certificate files end in a `.ca-bundle`, `.crt`, `.key`, or `.pem` suffix.

Changed
- You can now redeploy to a content with an "unknown" app mode. A content item's app mode is "unknown" if it was created, but never deployed to, or its deployment failed before an app mode could be determined.

Removed

- Python 3.5 & 3.6 support.

- `rsconnect-python` no longer considers the `RETICULATE_PYTHON` environment variable.
In environments where `RETICULATE_PYTHON` is set outside a project context (e.g. by a Posit Workbench administrator),
attempting to deploy content or write manifests in projects using virtual environments required explicitly setting `--python /path/to/virtualenv/python`.
Removing `RETICULATE_PYTHON` detection should simplify the use of the CLI in this case.

Added
- When running rsconnect bootstrap, you can now specify the jwt secret using the CONNECT_BOOTSTRAP_SECRETKEY environment variable.

Changed
- Update pip_freeze to use `pip freeze` since Connect filters for valid package paths in the backend and it no longer depends on the undocumented behavior of `pip list --format=freeze`. This reverts the change made in 1.5.2.

- Renamed the deploy_html `excludes` flag to `exclude` for consistency with other deploy commands.

Changed
- Updated actions.py to reuse code in main, minus the CLI parts. As a result deploy_jupyter_notebook and deploy_by_manifest had their return signatures changed. They now return None.