Integrate with iotedgehubdev

[LazarusX]

Currently there are 4 runtime control commands which need be ported for iotedgehubdev (for local development):

• start: wrapped iotedgehubdev start -d <path-to-deployment-manifest> and iotedgehubdev start -i <input name>, like iotedgedev start (pass deployment manifest path in .env as the <path-to-deployment-manifest> parameter or let users specify via CLI) and iotedgedev start -i <input name>
• stop: wrapped iotedgehubdev stop
• setup: iotedgedev setup wraps iotedgehubdev setup -c <connection-string> (pass device connection in .env as the parameter or let users specify via CLI)
• status: N/A, no status counterpart in iotedgehubdev yet.

[jongio]

@LazarusX Does start take in the runtime.json config or the deployment.json config?
Also, runtime.json is gone and replaced with YAML. Should we put a sample yaml in place of the runtime.json file?

[LazarusX]

start should take a deployment.json file. Yes, we can provide a sample runtime.json file.

[LazarusX]

Open a separate issue for IoT Edge GA bits #214 as it is planned post-GA, while focus this one on iotedgehubdev integration.