task: review IoTDB integration into WAII upstream and discuss possible merge

[slawr]

Some details of integrating a new State Storage backend into the WAII Service Manager are perhaps not documented.

Task outline:

• We should review the integration with upstream maintainers.
• Also discuss whether the new backends can be merged upstream.

Some possible areas for review:

1. Does setVehicleData() implementation meet WAII input/output requirements? e.g. is TS returned in correct format?
2. Does getVehicleData() implementation meet WAII input/output requirements? e.g. is TS returned in correct format?
3. Does ServiceMgrInit() implementation meet WAII requirements?
4. Does WAII have a debug logging mechanism that should be supported?

[slawr]

Pull request created in upstream project w3c/automotive-viss2#110 and discussion started with maintainers.

[slawr]

Upstream WAII project has merged the following PR's covering IoTDB:
Documentation: COVESA/vissr#2
Runtime config: COVESA/vissr#5
Add get/set support: w3c/automotive-viss2#110

I believe that covers all the basic bases for adding IoTDB support to WAII.
@UlfBj anything you think is missing before I close this?

[slawr]

The code has been merged upstream and no further review feedback from the upstream maintainers so closing this as done. With handle any follow up with new tasks