Provide explicit type mappings for ingested logs

[sopel]

While the implicit type mappings are sufficient for exploration, most more pronounced use cases imply drill down needs which almost always require wildcard based exclusions etc.

• This primarily blocks progress on As an AWS user, I want to analyze AWS CloudTrail logs so that I can reason about my account's security #2, but also impacts Provide geo locations for AWS resources #4 for similar reasons.

Accordingly, these need to be enabled via explicit mappings.

• ℹ️ Worth noting that the need for explicit mappings has come up in pretty much all logsearch-for-* sub projects and suggests a respectively generic approach for managing those accordingly.

[dpb587]

I've committed type mappings for the three current log types to ./src/logsearch-config/logs.