[CT-2255] Add retry logic to nightly installation tests

Recently, we've had a few transient installation failures due to network issues. We should probably add some retry logic to workflows called in [test-dbt-installation-main.yml](https://github.com/dbt-labs/actions/blob/main/.github/workflows/test-dbt-installation-main.yml).

This ticket will involve some exploration of how/when to retry

Start by reading .github/workflows/test-dbt-installation-main.yml and inspect the workflows it calls to identify where transient installation failures occur. Determine an appropriate retry point and verify that nightly installation tests retry network-related failures without masking persistent failures.

Written by the indexing model from the issue text.