Upstream mock sensor types to corresponding concrete sensor specs

[Honry]

Have a standalone issue for better tracking @anssiko's suggestion:

All - would you prefer to see mock sensor types (sections 9.1.3.*) integrated into corresponding concrete sensor specs? That might make maintenance easier if/when those specs add new API surface that need to be accompanied with corresponding new mock sensor reading values.

[anssiko]

Expanding a bit what I meant with "easier maintenance":

If we add mock sensor types into Generic Sensor API, that spec in practice turn into a "Living Standard", since every time a new concrete sensor is specified mock sensor types section need to be updated accordingly.

[anssiko]

I've now merged all the PRs to concrete sensors.

@Honry you can now create a PR to remove the text that was upstreamed to concrete sensors. Please check that the Bikeshed anchor data remains in a consistent state after the move is completed.

[Honry]

Thanks, @anssiko.

I've removed the text in #380, and one more concern in my mind, do we need to add a section to describe how to extend mock sensor type to extension specifications to the Extensibility?

[anssiko]

Yes indeed. Can you craft a separate PR for the extensibility section about that?

[Honry]

Sure!