fix(az-elasticpool): fix critical/warning threshold

[g-rei]

Description

The storage mode of Azure's Elasticpool plugin (cloud::azure::database::elasticpool::plugin) did not take warning and critical thresholds in consideration. To correct this, I've adapted the code of another Azure's Plugin.

Type of change

• Patch fixing an issue (non-breaking change)
• New functionality (non-breaking change)
• Breaking change (patch or feature) that might cause side effects breaking part of the Software

Target serie

• 22.04.x
• 22.10.x
• 23.04.x
• 23.10.x
• 24.04.x (master)

How this pull request can be tested ?

Please describe the procedure to verify that the goal of the PR is matched. Provide clear instructions so that it can be correctly tested.

You can simply test it by using this command :

perl centreon_plugins.pl --plugin=cloud::azure::database::elasticpool::plugin --custommode=api --mode=sessions
--resource='/subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Sql/servers/xxx/elasticpools/xxx'
--aggregation='average' --warning-storage-percent=70 --critical-storage-percent=90 --verbose

And then increase/decrease the values of warning-storage-percent or critical-storage-percent.

Checklist

Community contributors & Centreon team

• I have followed the coding style guidelines provided by Centreon
• I have commented my code, especially new classes, functions or any legacy code modified. (docblock)
• I have commented my code, especially hard-to-understand areas of the PR.
• I have rebased my development branch on the base branch (master, maintenance).