Telemetry/rework logs

[NelsonVides]

I also don't want logs to be raised by amoc. Logging might be desired to work differently, so instead of logs I'll also raise here telemetry events for internals, and in the subscribers I'll decide if I want to log something or not and how.

Split from #155 , uses #162

[DenysGonchar]

this PR requires rework.

[DenysGonchar]

it's just a general comment, and doesn't have to be implemented in this PR.
but but errors in update_fn for settings also deserve telemetry logging events. see store_scenario_config_and_run_update_functions/1 function in amoc_config_scenario module

[NelsonVides]

it's just a general comment, and doesn't have to implemented in this PR. but but errors in update_fn for settings also deserve telemetry logging events. see store_scenario_config_and_run_update_functions/1 function in amoc_config_scenario module

If it's not needed now I'll create a Jira ticket and we can discuss it any other time in the future 🙃

All other comments applied.

[codecov-commenter]

Codecov Report

Attention: 27 lines in your changes are missing coverage. Please review.

Comparison is base (c494c65) 33.23% compared to head (46ecf8f) 33.23%.
Report is 4 commits behind head on master.

Files	Patch %	Lines
src/amoc_throttle/amoc_throttle_process.erl	0.00%	20 Missing ⚠️
src/amoc_distribution/amoc_cluster.erl	0.00%	4 Missing ⚠️
src/amoc_config/amoc_config_verification.erl	0.00%	2 Missing ⚠️
src/amoc_config/amoc_config.erl	50.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #163   +/-   ##
=======================================
  Coverage   33.23%   33.23%           
=======================================
  Files          23       23           
  Lines         975      981    +6     
=======================================
+ Hits          324      326    +2     
- Misses        651      655    +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.