feat(rust): Redesigned agama logs command to have functionality in the backend and accessible via HTTP API

[mchf]

Problem

Agama's CLI logs command used to be implemented with idea CLI running on same machine as real installation (the backend). As this is not true anymore and we have installer's backend and frontend separated with HTTP API, which makes remote access possible, the logs command had to be updated to support this idea.

Its trello card

Solution

• the particular code which is in control of collecting logs was moved into agama-lib
• agama's web server has contains http(s):///api/logs piece in its public API
• agama's CLI uses the above API for downloading the logs

Testing

• Tested manually

[coveralls]

Pull Request Test Coverage Report for Build 11708505683

Details

• 0 of 171 (0.0%) changed or added relevant lines in 6 files are covered.
• 2 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.06%) to 71.429%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
rust/agama-cli/src/lib.rs	0	1	0.0%
rust/agama-lib/src/base_http_client.rs	0	5	0.0%
rust/agama-lib/src/manager/http_client.rs	0	16	0.0%
rust/agama-cli/src/logs.rs	0	23	0.0%
rust/agama-server/src/manager/web.rs	0	28	0.0%
rust/agama-lib/src/logs.rs	0	98	0.0%
<!--	Total:	0	171	0.0%	-->

Files with Coverage Reduction	New Missed Lines	%
rust/agama-cli/src/lib.rs	1	0.0%
rust/agama-cli/src/logs.rs	1	0.0%
<!--	Total:	2		-->

Totals
Change from base Build 11707344472:	-0.06%
Covered Lines:	16895
Relevant Lines:	23653

---

💛 - Coveralls