Add "skipped" conditional for near zero metric value fast fails

[DanielHHowell]

No description provided.

[linear]

ENG-565 Servox fast-fail logic for handling values/thresholds at or near zero

During release candidate testing for 2.4 we ran into a failing baseline validation stage caused by the error_rate fast fail configuration:

        - keep: below
          metric: tuning_error_rate
          threshold_metric: main_error_rate
          threshold_multiplier: 4
          trigger_count: 3
          trigger_window: 5

The problem was that main error_rate was 0 whereas tuning error rate was 0.009090909090909090467524933388. The tuning error rate is within acceptable margins but because 0.009090909090909090467524933388 > 4 * 0 it fast-failed the measurement and we need to add logic to the fast fail to ignore values less than 1 or provide some sort of minimum value (eg. 0.25) when the threshold_metrics is detected as 0

https://console.opsani.com/accounts/dev.opsani.com/applications/opsani-dev24-rc/logs?sort_by=-last_activity_time&show_apps=all&log_details_for=dfLK4rv7wgit03hCD9tf

[linkous8]

Please also add a new property to the FastFailConfiguration class that toggles whether to treat absolute zero values (== 0, not close to 0) as missing since some metric systems will return 0 for a metric that has data in the system even though it has no data/null data for the time frame being queried. The new configuration allows us to account for that as needed