Update swanky check

[codespool]

Overview (What and Why)

swanky check's output should simply list all the dependencies' versions, and list the eventual missing ones.
It should also include the OS and architecture info.

The output should also be optionally stored in a file, so it can be shared for debugging purposes

We should also maintain a remote compatibility list of cargo-contract version -> min ink! version that should be fetched and used when checking the local env, and warn the user to update the ink! version accordingly

How

• modify the command output to include install status and versions of all dependencies, including OS
• add optional file output
• host a cargo-contract -> ink dependency table
• fetch and store the dependency table on init and check use
• check local cargo-contract and contract's ink! versions against the table and warn user to update if needed

Definition of Done

• above implemented and merged
• docs updated

Open Issues and Blockers

[shunsukew]

Why not just use redirecting output swanky check > result.txt or use copy&paste?
I don't see any value of saving option.

[codespool]

If you output just plain text, that's an ok option, but if we add some formatting (f.ex. a table or some colours), then a redirect would have unnecessary formatting characters and --file option or similar would be used to print plain text to a file.

[vsofiya]

#195