Feature Request: improve "cannot run a document" message

Summary of the new feature/enhancement

I had to go look at the source code to understand what “cannot run a document” actually meant. Please consider rewording this. Perhaps - “cannot run a non-executable”.

Note that are two messages with this wording - CantActivateDocumentInPipeline and CantActivateDocumentInPowerShellCore.

https://github.com/PowerShell/PowerShell/blob/c909541b7797b60462188a4abe9592a8763c1fbb/src/System.Management.Automation/engine/NativeCommandProcessor.cs#L1133-L1146

[aelij]

@sdwheeler I find word “document” a bit confusing (and somewhat Windows-y 😃. Shells have files and executables. Even the PS error when it can’t find a command doesn’t use this word:

The term ‘foo’ is not recognized as a name of a cmdlet, function, script file, or executable program.

[sdwheeler]

PowerShell/src/System.Management.Automation/resources/ParserStrings.resx

Line 592:

  <data name="CantActivateDocumentInPipeline" xml:space="preserve">
    <value>Cannot run a document in the middle of a pipeline: {0}.</value>
  </data>

Suggested text: “Cannot invoke a document in the middle of a pipeline: {0}”

Line 1356:

  <data name="CantActivateDocumentInPowerShellCore" xml:space="preserve">
    <value>Cannot run a document in PowerShell: {0}.</value>
  </data>

Suggested text: “This platform does not support file handlers for document invocation: {0}”