TEMS ACC - Remote desktop and system properties collector

[BabaDorin]

The goal of this user story is to finalize the development of TEMS ACC.

In scope:

• Include remote desktop client
• Include machine diagnostics component (already developed by @skromn1k, but needs to be translated to Go)
• Include an UI component (Flutter, MAUI or WPF, @lbodlev888). My recommendation is to go with Flutter as it also natively supports Linux
• Integration of TEMS ACC with TEMS Platform

To be investigated: accountable @lbodlev888

• Secure connection between TEMS ACC and TEMS Platform for diagnostics transfer and remote desktop
• A DNS-like architecture - TEMS ACC platform address may change over time due to all sorts of reasons, therefore it may be necessary to have some sort of a DNS server of mapping ACC unique identifier with their tems HOST address, so they know what is the address of the TEMS platform without it being hardcoded in the ACC module, and it would allow to change the address of TEMS platform easily in the future, and ACCs will automatically get the new address.
• A documentation page on wiki for secure integration of TEMS ACC and TEMS Platform

About integration of TEMS ACC with TEMS Platform:

• Computers will send diagnostic information once a minute to TEMS Platform.
• Diagnostics data will be stored in mongo db, in a new dedicated collection: asset_diagnostics, with the structure:
  • asset_id
  • timestamp
  • diagnostics data model that is collected and aggregated (this model must be defined in TEMS ACC repository)
• Connecting to remote deskstop must be done directly from TEMS platform, without the need of installing additional software on technician side.