feat: add patch manager IaC

[jjfrench]

Description

• adds a maintenance window to perform patches on pgbouncer instances

[hrodmn]

Thanks for adding this! My only request is to export the pgbouncer instance names from the pgstacinfra stacks so we can provide the full names as props instead of just the stage name.

Do you think any of this could/should be fed back into eoapi-cdk's pgbouncer infrastructure?

[hrodmn]

I think it would be best to provide the full instance names via props instead of just the stage. You might need to export the instance names in the other stack but it would be safer in case those instance names change for some reason.

[jjfrench]

Fair enough, I didn't add the condition to check that the other stack existed first but I can add that and export the name.

[jjfrench]

Do you think any of this could/should be fed back into eoapi-cdk's pgbouncer infrastructure?

I think that it should in some sense, but looking at how we deploy the infrastructure it got a little messy when I was first defining it. I wouldn't want multiple maintenance windows/patch managers for our use case - one pgSTAC and one userSTAC but both are technically one environment. Do you think there's a way to define this infrastructure alongside the pgbouncer constructs without generating multiple maintenance windows/patch managers? or do you think I should add an optional default one that we wouldn't use in our case?

[hrodmn]

Do you think there's a way to define this infrastructure alongside the pgbouncer constructs without generating multiple maintenance windows/patch managers? or do you think I should add an optional default one that we wouldn't use in our case?

I think it would make sense to add the capability to eoapi-cdk when pgbouncer is enabled since it shouldn't incur much cost (right?). I see why you would just want the one patch manager in this case, so maybe it would be nice to make it togglable.