Removing dependencies check, adding a link to documentation page

[AR-May]

Concerns issues #6, #36, #72.

The dependencies check is currently broken:

• it is out of date,
• it is not full (and can't be full): for different versions, for runtime/SDK, there might be different sets of dependencies,
• the warnings are misleading, as they do not specify that it is a library name, not a package name, which has not been found.

To support these checks properly (more/less full and not out of date) we would need too big of an effort. It is doubtful that some checks always are better than none: we are worried that the customer would see the warning, add the library, and would not understand why dotnet still does not work, as a result of incompleteness of a check.

Based on these, we decided to remove them and instead always ask the customer to visit the documentation page and to check the dependencies listed there.

[donJoseLuis]

Thanks for moving this forward. We definitely need @bozturkMSFT 's signoff.

[genalt]

LGTM