chore(e2e): Get logs from postgres container to debug deadlock errors

[moduli]

This PR updates the GitHub Action workflow that runs the e2e tests to grab logs from the postgres container. Hopefully, this will shed some light on a flaky deadlock error we've been seeing.

Messages:   	Error from controller when performing delete on scope
        	            	
        	            	Error information:
        	            	  Kind:                Internal
        	            	  Message:             scope.(Service).deleteFromRepo: unable to delete scope:
        	            	  iam.(Repository).DeleteScope: failed for o_TG0TF3JWcq:
        	            	  iam.(Repository).delete: db.DoTx: iam.(Repository).delete: db.Delete: unknown,
        	            	  unknown: error #0: dbw.Delete: ERROR: deadlock detected (SQLSTATE 40P01)
        	            	  Status:              500
        	            	  context:             Error from controller when performing delete on scope

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
boundary	⬜️ Ignored (Inspect)		Oct 3, 2023 1:43pm

[tmessi]

Where does the config for this container live? I just want to double check is logging configuration to see if we should adjust anything there.

[moduli]

@tmessi This is the terraform that spins up the container: https://github.com/hashicorp/boundary/blob/main/enos/modules/docker_postgres/main.tf

Here's an example run that has the logs output: https://github.com/hashicorp/boundary/actions/runs/6386050996/job/17332494723

[tmessi]

Ok yea that config looks good.