[OTE] Update OpenVINO to 2022.3 release

[sovrasov]

• Update OV
• Update NNCF, corresponding fixes in d-o-r
• Minor fixes in readmes
• Changes from [DEV] Fix nncf config for padim model #1487

[sovrasov]

run ote-test

[sovrasov]

run ote-test

[sovrasov]

run ote-test

[sovrasov]

run ote-test

[sovrasov]

run ote-test

[sovrasov]

run ote-test

[sovrasov]

run ote-test

[sovrasov]

run ote-test

[sovrasov]

run ote-test

[sovrasov]

run ote-test

[sovrasov]

run ote-test

[sovrasov]

run ote-test

[sovrasov]

run ote-test

[sovrasov]

Build: https://ci-ote.iotg.sclab.intel.com/job/ote/job/pr-ote-test/872/

[goodsong81]

LGTM!

[sungmanc]

LGTM

[samet-akcay]

@sovrasov, @goodsong81, do you guys know why we need to install both openvino and openvino-dev? Is there any specific motivation to have this installation? Can't we just do pip install openvino["dev"] that would install the dev package as well as the base openvino ? Or why openvino-dev does not install the base openvino? Any ideas, thoughts?

[sovrasov]

Hi Samet, you're right, we can omit openvino if we have openvino-dev. openvino package version is always presented here for clarity and historically we always added it implicitly. Perhaps, we may change that in otx.

[samet-akcay]

Vlad, thanks for the clarification!

openvino package version is always presented here for clarity and historically we always added it implicitly.

To be honest, it caused more confusion to me than clarity. I would agree to only keep openvino-dev if it also installs the base openvino. This way, we would get rid of one more dependency, wouldn't need to maintain version numbers etc.