[Winlogbeat] Non-namespaced fields in PowerShell modules fields.yml

[andrewkroh]

The PowerShell module's fields.yml is including some fields that are not namespaced under powershell.*. I think this is just a mistake in the fields.yml and not a problem with the actual data being produced by the module.

Looking at winlogbeat export template:

          "winlog.user.type",
          "id",                   <----
          "pipeline_id",          <----
          "runspace_id",          <----
          "powershell.command.path",
          "powershell.command.name",
          "powershell.command.type",
          "powershell.command.value",
          "powershell.command.invocation_details.type",
          "powershell.command.invocation_details.related_command",
          "powershell.command.invocation_details.name",
          "powershell.command.invocation_details.value",
          "powershell.connected_user.domain",
          "powershell.connected_user.name",
          "powershell.engine.version",
          "powershell.engine.previous_state",
          "powershell.engine.new_state",
          "powershell.file.script_block_id",
          "powershell.file.script_block_text",
          "powershell.process.executable_version",
          "powershell.provider.new_state",
          "powershell.provider.name",

[elasticmachine]

Pinging @elastic/siem (Team:SIEM)