Create rule "External worker process"

[agoncal]

While it is possible to launch new worker processes in either Azure App Service or Azure Kubernetes Service environments, it is an anti-pattern to do so. Both expect to have a single process running and launching others can make it difficult to manage and debug the applications. Expecting another process or service to already be running in parallel with the service will not work in Azure App Service and is an anti-pattern in Kubernetes.

Such metadata in .NET apps can be detected by identifying usage of the System.Diagnostics.Process class.

PRs

Beta Give feedback

1. Check if external process is started in java code windup/windup-rulesets#995
   Ready to Review +1
2. add azure-jni-native-code rule windup/windup-rulesets#967
   +0
3. Overrides the existing JNI Native code rule windup-rulesets#90
   rule +1
   
4. Refactors the existing JNI rule windup-rulesets#72
   rule +1
   

[showpune]

Customer use
···java
Process p = Runtime.getRuntime().exec(exec);
···java
to execute some worker process

[agoncal]

I reopened it because I realized that there is a pending PR on the WindUp side: windup/windup-rulesets#995