Boundaries for the time period

[FabrizioMoggio]

The time period supported by the platform could be limited so an error code must be return if the time period requested exceed what supported by the platform.

The returned error code could be: Generic400 with code: OUT_OF_RANGE

[FabrizioMoggio]

This must be documented in the .features files in the "Rainy Days" section not due for Fall25

[FabrizioMoggio]

maybe even some report should be provided about the valid "start date" and "end date" supported for that application.

[FabrizioMoggio]

OUT_OF_RANGE should be returned if:

1. timePeriod is greater then the supported one
2. the "end date" is in the future

[FabrizioMoggio]

The monitoring of the energy consumption starts when the App Provider subscribes the EFN API otherwise we should collect all the data for all the Apps even if no one is interested in the energy consumption. I will enhance the text in the YAML to clarify this.

[FabrizioMoggio]

proposal: add this feature in the Sync26 release