Update schema to allow isolated-day-peak models

[elden1337]

In Sweden, there are emerging tariff models that do not bill a ”remembered” value as monthly max or average of 3 daily peaks, but rather an isolated calculation per day, which then sums up at months end.
This poses a problem to the current schema, as it cannot distinguish between these variants.

Below is a proposed change that should reveal the variants:

Version 1 (Aggregation = 1 peak per day)

{
  "peakIdentificationSettings": {
    "identification": {
      "period": "P1D",
      "duration": "PT1H"
    },
    "billing": {
      "billingPeriod": "P1M",
      "billingAggregationPeriod": "P1D",
      "numberOfPeaksForAverageCalculation": 1
    }
  }
}

Version 2 (Aggregation = 3 peaks per month)

{
  "peakIdentificationSettings": {
    "identification": {
      "period": "P1D",
      "duration": "PT1H"
    },
    "billing": {
      "billingPeriod": "P1M",
      "billingAggregationPeriod": "P1M",
      "numberOfPeaksForAverageCalculation": 3
    }
  }
}

This should cover the existing models as well as the new variant with isolated daily billing-calculations.

[larwa99]

There is a tariff.billingPeriod already, but having it per component makes sense to support more scenarios.

[larwa99]

To allow for a "rolling hour" that does not always start at full hour, perhaps a durationOffset (default = PT0M) could be introduced?

{
  "peakIdentificationSettings": {
    "identification": {
      "period": "P1D",
      "duration": "PT1H",
      "durationOffset": "PT0M|PT15M|PT30M|PT45M"
    },
    "billing": {
      "billingPeriod": "P1M",
      "billingAggregationPeriod": "P1D",
      "numberOfPeaksForAverageCalculation": 1
    }
  }
}