test unhealthy shares

[petrkalos]

Feature or Bugfix

• Feature

Detail

New tests

• deliberately break shares (by removing permissions
• run the verifier to assert that are unhealthy
• run the reapplier to assert that they can be fixed

Imrpovements

• Drop updated_persistent env and always update the persitent_env on get_or_create_env()
• Use contextmanagers to create environments and handle their lifecycle in one place
• Make redshift tests optional based on configuration

Relates

Solves parts of #1376

Security

Please answer the questions below briefly where applicable, or write N/A. Based on OWASP 10.

• Does this PR introduce or modify any input fields or queries - this includes fetching data from storage outside the application (e.g. a database, an S3 bucket)?
  • Is the input sanitized?
  • What precautions are you taking before deserializing the data you consume?
  • Is injection prevented by parametrizing queries?
  • Have you ensured no eval or similar functions are used?
• Does this PR introduce any functionality or component that requires authorization?
  • How have you ensured it respects the existing AuthN/AuthZ mechanisms?
  • Are you logging failed auth attempts?
• Are you using or adding any cryptographic features?
  • Do you use a standard proven implementations?
  • Are the used keys controlled by the customer? Where are they stored?
• Are you introducing any new policies/roles/users?
  • Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.