Docs/fix various api doc issues

[nhoening]

Description

Fix a few incorrect issues in documentation (focus: API).

• add sensor ID to schema in asset's schedule-triggering endpoint
• add deprecation header and info to schedule-triggering endpoint on sensor
• state-of-charge field: the sensor needs an instantanious resolution
• _scheduling_resolution links are broken
• soc minima in API docs mention a datetime field while the correct ones are start and end?
• Added changelog item in documentation/changelog.rst

[read-the-docs-community]

Documentation build overview

📚 flexmeasures | 🛠️ Build #32327799 | 📁 Comparing b28b6d3 against latest (2ad5dee)

  🔍 Preview build  

4 files changed

± http-routingtable.html
± _autosummary/flexmeasures.api.common.schemas.utils.html
± _autosummary/flexmeasures.api.v3_0.sensors.html
± api/v3_0.html

[Flix6x]

add deprecation header and info to schedule-triggering endpoint on sensor

I would recommend already moving the flexmeasures-client to always use the new endpoint under the hood. I created FlexMeasures/flexmeasures-client#195 accordingly.

[Flix6x]

Yes, seems right for this version. In #2190 I started working on making the sensor field more explicitly part of the schema, but moved to implement the consumption and production fields instead.