API endpoint for scheduling asset

[Flix6x]

Description

Schedule an asset using a flex-model that consists of a list of flex-models for individual power sensors.

In this PR:

• [F] Create new API endpoint
• [F] Documentation of endpoint
• [F] Extend battery+PV tutorial
• [F] Ensure that flexible sensors fall under the asset (inflexible sensors may still come from a different asset)
• [V] Test scheduling API with 2 flexible sensors

Other work done here, but then moved to #1313 (already on main):

• [F] Marshmallow validation
• [F] Unpack flex-model into one flex-model per sensor
• [V] Dependent scheduling jobs
• [V] Test scheduling service with 2 flexible sensors

Look & Feel

URI: assets/801/schedules/trigger

Body:

{
    "flex-model" : [
        {"sensor" : 1, "power-capacity" : "1MW"},
        {"sensor" : 2, "power-capacity" : "10kW"},
        {"sensor" : 3, "soc-at-start" : 10.0},
    ],
    "flex-context" : {
        "consumption-price-sensor" : 8,
        "production-price-sensor" : 9,
        "inflexible-device-sensors" : [14, 15]
    }
}

Further Improvements

Created follow-up issues:

• [F] Check user is authorized to reference sensors in flex-model and flex-context: moved to 904 read permissions of entities within flex model or flex context #1071
• CLI needs option to set model and context from file (editable?): CLI: add schedule w/ complete flex context and model #1431
• [F] Integration test that resembles toy tutorial case (battery + solar + EV): moved to Integration test that resembles toy tutorial case (battery + solar + EV) #1542

Related Items

Closes #485.

[nhoening]

CLI needs option to set model and context from file (editable?)

I believe this is #1431

[nhoening]

Thanks for all the improvements.

Only quite minor comments.

[nhoening]

I already approve, feel free to use my suggestion and answer my only remaining question.

Happy to see us starting to test this in real cases with the whole stack!