[ECI-396] Add logging module

[sva91]

What

• Get All log groups in tenancy, and get all logs from log groups. This is required because log resources for resources from which we want to forward logs maybe present in other compartments.
• Add timeCreated field for resources in discovery. This helps add deterministic behavior for log creation
• Add logging module

1. It takes in resources from which logs should be forwarded for a compartment, all existing log resources in tenancy and services from which logs need to be forwarded.
2. It finds existing loggroups from which logs should be forwarded.
3. It creates a new log group "datadog-service-logs" in the compartment.
4. It generates log resources for resources which don't have logging already enabled.
5. It outputs existing loggroups and loggroup id for the newly created "datadog-service-logs" group.

Why

• Setting up infrastructure for log forwarding

Testing

1. Base Case : Stack Link
2. Re-execution of stack with more compartments: If more compartments are added in compartments csv and stack is reexecuted, logs from new compartments will be generated, and nothing will happen to existing log resources.
3. Re-execution of stack with no variables changed: New resources generated since the last execution will be found, and log forwarding will be setup from these new resources
4. Re-execution of stack with change in exclude_services variable : This should also be honored correctly, although we might regenerate some log resources in this case.

Issues Fixed During Testing

• Display Name of resource may have a space. To derive log resource display name from resource name, replace " " with "_".
• Resource Types from resourcediscovery may be Camelcase. Make them lower case to match existing log resources.
• Objectstorage is a special case requiring resource.display_name instead of resource.id, in order to generate logging resource.
• If there is a log-category = "all", we can't enable specific categories. For example, for flowlogs, categories = ["all", "flowlogs"]. We only need to enable logs of "all" category, which collects information for the entire service. This is now handled in the code.

[bengillmandd]

Just had a couple of nitpicks. I'm not the best person to review this so might be good to get Kanishk's review too

[bengillmandd]

This exists already for audit logs yeah? That is why we don't need to create this for audit logs too?

[sva91]

Yes, that's correct. Audit Log group for a compartment is created when the compartment itself is created.