[CT-903] Configure more connection retries for CI tests

[nathaniel-may]

The upstream postgres adapter just added exponential backoff when retries > 1. We should change our retries settings for our dbt projects that run in CI to reduce RedShift failures. I suspect that can be set somewhere in here.

[jtcohen6]

Needs to be added in two places, since we have two test frameworks :)

dbt-redshift/tests/conftest.py

Lines 9 to 21 in 7abf046

	# The profile dictionary, used to write out profiles.yml
	@pytest.fixture(scope="class")
	def dbt_profile_target():
	return {
	'type': 'redshift',
	'threads': 1,
	'host': os.getenv('REDSHIFT_TEST_HOST'),
	'port': int(os.getenv('REDSHIFT_TEST_PORT')),
	'user': os.getenv('REDSHIFT_TEST_USER'),
	'pass': os.getenv('REDSHIFT_TEST_PASS'),
	'dbname': os.getenv('REDSHIFT_TEST_DBNAME'),
	}

dbt-redshift/tests/integration/base.py

Lines 146 to 166 in 7abf046

	def redshift_profile(self):
	return {
	'config': {
	'send_anonymous_usage_stats': False
	},
	'test': {
	'outputs': {
	'default2': {
	'type': 'redshift',
	'threads': 1,
	'host': os.getenv('REDSHIFT_TEST_HOST'),
	'port': int(os.getenv('REDSHIFT_TEST_PORT')),
	'user': os.getenv('REDSHIFT_TEST_USER'),
	'pass': os.getenv('REDSHIFT_TEST_PASS'),
	'dbname': os.getenv('REDSHIFT_TEST_DBNAME'),
	'schema': self.unique_schema()
	}
	},
	'target': 'default2'
	}
	}