Use sc-machine exported targets in the build system

[FallenChromium]

Is your feature request related to a problem? Please describe.
Currently, it's complicated to build sc-component-manager and test it without a specialized environment and build scripts such as ostis-metasystem. It might complicate development efforts and reduce developer productivity through absence of proper developer tooling support and complicated setup instructions.

Describe the solution you'd like
sc-machine has to export public targets that are being used by this project so that the build system will be the single source of truth on why something is or is not building inside sc-component-manager. We shouldn't rely on some third-party entity to build all dependencies for us - the build system of the sc-component-manager should know in which context does it run (where's the sc-machine installation, for example) and configure itself accordingly (including fetching / building sc-machine if required)

Describe alternatives you've considered
https://cmake.org/cmake/help/latest/module/ExternalProject.html
https://cliutils.gitlab.io/modern-cmake/chapters/install.html
https://cmake.org/cmake/help/latest/guide/importing-exporting/index.html