Sugguest native (PowerShell) command alternatives to CMD/Unix commands

Summary of the new feature

Following a idea and short chat with @SteveL-MSFT on twitter it occured to me that it might be a fit for PSScriptAnalyzer (see https://twitter.com/Steve_MSFT/status/1083749912439808001 )

I was reminded of a old pdf Ashley McGlone did https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/telligent.evolution.components.attachments/01/8458/00/00/03/54/23/12/PowerShell%20Cmd%20Line%20Conversion%20Guide%20AD.pdf (found on https://blogs.technet.microsoft.com/ashleymcglone/2013/01/02/free-download-cmd-to-powershell-guide-for-ad/ )

It can be hard to discover native PowerShell commands for commands you have used for years in cmd. Example ipconfig (or ifconfig) (if your new to PowerShell you might not even know.

There's a huge difference between getting the non structured text output from ipconfig and the objects you get from the native commands.

Say a user try to find IP of localhost by using ipconfig in his code PowerShell code. The script analyzer could sugguest using one of the commands above (or even Get-NetIPAddress) as an alternative that will return a object instead of "unstructured" text.

I'm not sure how to come up with a list of comparable commands, but I guess that is excatly why it might be nice.

Proposed technical implementation details (optional)

If the script analyzer could make alternatives visible e.g. in VS Code it might help people out.

El issue propone sugerencias del analyzer para alternativas nativas de PowerShell a los comandos de CMD y Unix, utilizando las asignaciones de ipconfig como ejemplo. No se han identificado archivos del repositorio, pruebas ni puntos de entrada del analyzer; primero define las asignaciones de comandos compatibles y localiza el punto de extensión relevante del analyzer, después establece cómo deben aparecer las sugerencias en VS Code y cómo se verificará la finalización.