Feature/s3 utils 158/storage consumption metrics

[benzekrimaha]

This PR aims to provide monitoring metrics for the count items cron-job.
Today the metrics that have been put in place are :

• bucketCount : Total number of buckets

• bucketProcessingDuration : Duration of processing a bucket

• consolidationDuration : Duration of metrics consolidation in seconds

• workersCount : a metric that shows success / errors during the workers count

• objectsCount : Number of objects based on their states

• metricsCount : Number of buckets ( none empty) , number of accounts with buckets , and number of locations

• It also puts in place a job stop mecanism resumed with :
  ==> If the job completed and the scraping occured => immediate stop
  ==> Otherwise we wait for a duration ( threshold x frequency x 4 x 1000 ) if a scraping occurs during it we stop otherwise we wait for the whole duration then we stop the job

Note for reviewers : this is a first iteration as the job has never been monitored ( only alerts were put in place ) please let me know if you see that some metrics might make more sens / or others are not really needed

Linked issue : https://scality.atlassian.net/browse/S3UTILS-158

[bert-e]

Hello benzekrimaha,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

[williamlardier]

Adding a comment as discussed: we need to set the counters/gauges to 0 at the beginning of a count-items run, otherwise the values will only increase

[benzekrimaha]

/create_integration_branches

[bert-e]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge feature/S3UTILS-158/storage-consumption-metrics into
  development/1.14
• w/1.15/feature/S3UTILS-158/storage-consumption-metrics will be merged into development/1.15

The following branches will NOT be impacted:

• development/1.13
• development/1.4

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: create_integration_branches

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

The following options are set: create_integration_branches

[benzekrimaha]

@bert-e create_pull_requests

[bert-e]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge feature/S3UTILS-158/storage-consumption-metrics into
  development/1.14
• w/1.15/feature/S3UTILS-158/storage-consumption-metrics will be merged into development/1.15 (pull request INTEGRATION [PR#312 > development/1.15] Feature/s3 utils 158/storage consumption metrics #313)

The following branches will NOT be impacted:

• development/1.13
• development/1.4

Follow integration pull requests if you would like to be notified of
build statuses by email.

The following options are set: create_pull_requests, create_integration_branches

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

The following options are set: create_pull_requests, create_integration_branches

[benzekrimaha]

/approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/1.14

• ✔️ development/1.15

The following branches have NOT changed:

• development/1.13
• development/1.4

Please check the status of the associated issue S3UTILS-158.

Goodbye benzekrimaha.

The following options are set: approve, create_pull_requests, create_integration_branches