Enhance ECS fields for Windows Event code 7045

User reporting the following behavior and suggested enhancements:

- When event.code is 7045, there is a `winlog.user.name`, but there is no `user.name` or `process.pid`.
- Also with event.code 7045, https://docs.elastic.co/en/integrations/windows suggests that there should be a `windows.service.name`, but there isn’t.
- In cases where using Winlogbeat and Logstash rather than Fleet/Elastic Agent, it's possible to apply some lookup tables to translate `event.code` into a more descriptive text string.
- There appear to be places where the integration is leaving data in `winlog.event_data.paramX` rather than translating it into its final ECS position such as `service.name`, `registry.path`, `registry.value`, etc.

cc @jamiehynds