Merge of UI & service CICD infrastructure and pipelines

[brucehyslop]

• merges the lists-service/cicd & lists-ui/cicd into a common root cicd directory.
• split the out resources from base component:
  • ECR into its own ecr CF template
  • db-password secrets manager into database CF template
• base component only contains setup of cognito app client
• moved ecr CF template into build pipeline, the ECR is a dependency of the build process
• moved the database CF template into the deploy pipeline, the database is a dependency of the deploy process
• changed frontend build pipeline to reference app client from base stack

[joe-lipson]

Nice work on the merge. I like having the app client as it's own standalone CF template, or more accurately of all the options I dislike it the least! :D CF feels more stable than CLI in managing resources as far as lifecycle and also seeing what's under management, it's nice not to have to shuffle nested stacks around from the cognito repo and reference them too.

as far as shuffling some of the resources between components, I think it's good to be flexible and put them wherever fits best. It's gong to work either way but I reckon the DB should be it's own component still, it's something that we'd launch once and then only relaunch/update very infrequently. The deploy component is something that will launch a lot more often, if the DB is part of that it will slow the deploy down, I guess not that much if there's no updates but it just seems unnecessary as it will still have to check every time. With the secrets being in the DB stack there are other secrets like oidc-secrets that make it more of a common resource