SSH Runner: Fix several issues and refactor code

[perseoGI]

Changelog: Feature: Introducing SSH runner
Docs: conan-io/docs#3972

Changes:

• Fix creation of virtual environment
• Retrieve current conan client version and install remotely if it does not exist
• Error checks
• Create a custom SSH Logger based on ConanOutput
• Properly manage build and host profiles, copying to the runner machine if needed and keeping the jinja2 templates intact to allow remote runner to render them locally
• General code refactor: some improvements like typing and simplifying code flow
• Fix cache inconsistency when a package have been created remotely and already restored the cache locally. If the package is removed locally, the runner was never bringing the package back to local. This happens because it only compress the build recipes. Solved by always exporting all the packages and forcing a local cache refresh
• Correctly manage special characters like & and * during ssh remote invoques
• Add configuration to conan config list
• Refactor configuration options structure to be under runner.ssh key
• Add different runner types detection on profile composition

• Refer to the issue that supports this Pull Request.
• If the issue has missing info, explain the purpose/use case/pain/need that covers this Pull Request.
• I've read the Contributing guide.
• I've followed the PEP8 style guides for Python code.
• I've opened another PR in the Conan docs repo to the develop branch, documenting this one.

[memsharded]

Avoid formatting and typing changes, it makes difficult to read the changelog and check if some new argument was added to the constructor

[davidsanfal]

We need to discuss if we want to copy the profiles to the host. (templates, etc) and if we want to add the config to the builtins (same for docker).

[memsharded]

I don't think this ssh runner should have the responsibility to install Conan in the remote machine, lets keep it as minimal as possible.

[perseoGI]

This behavior is present in develop2, not a new introduction.
The main idea is that the SSH runner will create a completely isolated environment and a completely isolated Conan installation to avoid any possible interference with the host machine.
Also, the installed conan version should match the caller version.