Add Nightly Deploy Tests

[kgartland-rstudio]

Intent

This PR adds deployment tests to run at night against a fuzzbucket instance running Connect.

Workflows:

• nightly.yaml: This runs at 1 AM EST and kicks off all the tests and build workflows that the pull-request.yaml runs as well as the contract-deps, contract, cleanup
• contract-deps.yaml: currently this only contains a way to start a fuzzbucket instance running Connect. In the future, we can add ways to run other deployment targets and their dependencies here.
• contract: this is where we run the new test-deploy target that kicks off deployments from the publish-ui to our new fuzzbucket instance we started in contract-deps
• cleanup: this stops the fuzzbucket instance we started.

Cypress Tests:

• contract: This currently contains only one spec that deploys the content, then checks to ensure the content was deployed properly to our fuzzbucket instance.
• ui: I also split out the existing home spec into a ui folder. Tests in the ui folder will test the local publish-ui without the need to have a running Connect instance for deployments.

The pull-request and main workflows will continue to run the ui tests but not the contract tests since these take longer to run due to fuzzbucket startups. and rely on network connections.

Setup:
test/setup/ folder contains scripts to install the latest available dev version of Connect and gets the address using fuzzbucket (connect_setup.py) and a script to calculate an api key given a username (gen_apikey.py). We then store the Connect address as CONNECT_SERVER and the api key as CONNECT_API_KEY so we can use the -n env flag to publish content. This may change in the future when we have better ways to add accounts.

Fuzzbucket:
The fuzzbucket instance I created is called ubuntu22-publishing-client. It has 3 users (admin, publisher, viewer) and I pre-deployed content to build caches for each of the Connect jumpstart examples so deploys won't take long in the contract tests mentioned above. It currently has Python 3.11.4 and R 4.1.2.

Type of Change

• Bug Fix
• New Feature
• Breaking Change

Approach

Automated Tests

Directions for Reviewers

Checklist

• I have updated CHANGELOG.md to cover notable changes.

[sagerb]

Looks good to me! I left a note on the impact of our redesign, but the impact on this code shouldn't be too bad. I would recommend holding off on adding additional UX cypress tests until we get the new UX up and running.

[sagerb]

Just a note, this is going to be broken and require updates when the new UX design gets merged into main. The default UX will require navigation from the project page to the pre-publish page, where the publish button will be located. We will eventually provide some routes to get directly to the pre-publish page, but those may not be there to start with. No change needed for this PR, but I wanted to let you know.

[kgartland-rstudio]

Sounds good. It shouldn't impact CI workflows, we'll just have some nightly failures for a bit until it's ready.