Cloud runner develop v0.1

[frostebite]

• Cancel follow logs flag now requires cloudRunnerIntegrationTests flag to avoid accidental triggering
• Link to AWS Cloud Watch logs fixed
• Cleanup pipeline now uses AWS list all CLI command which includes info about resource age for monitoring

[github-actions]

[codecov-commenter]

Codecov Report

Merging #395 (bb93233) into main (4556fc4) will decrease coverage by 0.94%.
The diff coverage is 17.47%.

@@            Coverage Diff             @@
##             main     #395      +/-   ##
==========================================
- Coverage   53.30%   52.36%   -0.95%     
==========================================
  Files          64       65       +1     
  Lines        1994     2049      +55     
  Branches      368      385      +17     
==========================================
+ Hits         1063     1073      +10     
- Misses        871      914      +43     
- Partials       60       62       +2     

Impacted Files	Coverage Δ
src/model/cloud-runner/providers/k8s/index.ts	12.00% <ø> (ø)
...-runner/providers/aws/commands/aws-cli-commands.ts	12.38% <12.69%> (-4.29%)	⬇️
...cloud-runner/services/follow-log-stream-service.ts	17.85% <17.85%> (ø)
...odel/cloud-runner/providers/aws/aws-task-runner.ts	9.00% <20.00%> (+1.50%)	⬆️
...oud-runner/providers/k8s/kubernetes-task-runner.ts	14.54% <25.00%> (ø)
src/model/build-parameters.ts	95.34% <100.00%> (ø)
...iders/aws/cloud-formations/base-stack-formation.ts	100.00% <100.00%> (ø)
.../aws/cloud-formations/task-definition-formation.ts	100.00% <100.00%> (ø)

[frostebite]

Currently the AWS pipelines fail because I deleted the base stack to cleanup and test from scratch.

But this doesn't delete the AWS VPCs it seems, now I have reached the max 5 I can create. And deleting them is blocked because you must first delete dependent resources.

I will work through that shortly and reinitialize the base stack.