Exec action should expose the created process id

[end2endzone]

Is your feature request related to a problem? Please describe.
The <exec> action should expose the created process id. The process id is printed in the logs but it is not exposed as a property. Exposing the process id allow users to create menus that start and stop processes.

Describe the solution you'd like
A pid attribute which specifies the name of the property to set to the created process id.

<exec path="C:\Windows\System32\calc.exe" pid="calc.process.id" />

Describe alternatives you've considered
N/A

Additional context
N/A

[end2endzone]

TODO:

• Change sample program from calc.exe to mspaint.exe.

Calc.exe is a bad example to use. calc.exe is a stub/proxy which will launch the actual CalculatorApp.exe. For my system, thats is C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_11.2405.2.0_x64__8wekyb3d8bbwe\CalculatorApp.exe.
However, a normal user cannot launch this process:

Windows cannot access the specified device, path, or file.You may not have the appropriate permissions to access the item.

See https://stackoverflow.com/questions/63990787/the-process-id-returned-by-the-createprocess-function-is-different-from-the-task for details.

Also it is better to use mspaint.exe than notepad.exe while starting/stopping processes while running unit tests because mspaint.exe is much less likely to be already running than notepad.exe.