What does this PR do?

Explicit mapping for all osquery fields.

Following this recommendation for mapping
https://www.elastic.co/guide/en/elasticsearch/reference/current/number.html

Consider mapping a numeric identifier as a keyword if:
You don’t plan to search for the identifier data using range queries.
Fast retrieval is important. term query searches on keyword fields are often faster than term searches on numeric fields.
If you’re unsure which to use, you can use a multi-field to map the data as both a keyword and a numeric data type.

The fields mapping is generated from the official osquery 4.7.0 schema. The numeric fields are mapped to keywords, the text fields had additional text multifield defined.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.

Author's Checklist

Related issues

• Relates https://github.com/elastic/security-team/issues/935

Screenshots

osquery mapping:

collected osquery data with types converted appropriately with osquerybeat