feat(logging): using init-fluent-bit images

[thisismana]

Migrate to Init Process of AWS for Fluent-Bit Image.

We now use the official image and bootstrap it with centralized configs that support our use case (json and envoy logs).

Context: https://github.com/aws/aws-for-fluent-bit/tree/develop/use_cases/init-process-for-fluent-bit

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[moritzzimmer]

Not stale

[moritzzimmer]

@thisismana @saefty I pushed a proposal which allows dynamic configuration of S3 or image local init config files on the client side including (least priviledge) IAM permission for S3 config files.

Example usage on the client side:

init_config_files = [
      "arn:aws:s3:::config-${var.account_id}-${var.region}/ecs/fluent-bit/service-custom.conf",
      "arn:aws:s3:::config-${var.account_id}-${var.region}/ecs/fluent-bit/filters-custom.conf",
      "arn:aws:s3:::config-${var.account_id}-${var.region}/ecs/fluent-bit/parsers-custom.conf",
      "arn:aws:s3:::foo-${var.account_id}-${var.region}/ecs/fluent-bit/parsers-custom.conf",
      "/ecs/s3.conf"
    ]

What do you think?