[Tracking Issue] Improved UX (yagna, ya-provider)

[mfranciszkiewicz]

Provider:

1. Providers offer resources requested in a Demand, instead of all specified in a preset.
2. Providers track the used hardware resources and allow execution of more than one activity at a time, depending on the amount of resources left.
3. Providers are not paid for failures in starting the ExeUnit
4. poor UX: http errors reported as warnings for something that's "normal operation" #1706
5. Add a provider command to list payments going into this specific node. #1770
6. [handbook] Create ya-provider chapter yagna-docs#82
7. [Feature Request] Allow a golem provider to cleanly shutdown i.e. set it to complete current task but not accept new ones. #1840
8. Misleading Provider CPU/h naming #1894
9. Provider graceful shutdown #1922

Why:

1. Providers often overcommit available resources available for a task. E.g. "simple service" may allocate 64 CPU cores for the VM.
2. Unused hardware resources may be assigned to another activity, increasing Provider's income.
3. (TBD) Protects Requestors from malicious Providers, who extort the initialization fee (and potentially a small amount of CPU time / RAM / etc.)

Yagna:

• when unlocking a key, use the encryption parameters saved inside the keystore file #1767
• Research - include gas costs in allocation budget #1741
• GSB endpoints for all CLI commands #1915

ExeUnit

• Deploy and Transfer command authorization using API token #2063