Update OV to 2023.1

[sovrasov]

Summary

This PR upgrades OpenVINO to 2023.1

How to test

Checklist

• I have added unit tests to cover my changes.​
• I have added integration tests to cover my changes.​
• I have added e2e tests for validation.
• I have added the description of my changes into CHANGELOG in my target branch (e.g., CHANGELOG in develop).​
• I have updated the documentation in my target branch accordingly (e.g., documentation in develop).
• I have linked related issues.

License

• I submit my code changes under the same Apache License that covers the project.
  Feel free to contact the maintainers if that's a concern.
• I have updated the license header for each file (see an example below).

# Copyright (C) 2023 Intel Corporation
# SPDX-License-Identifier: Apache-2.0

[sovrasov]

@yunchu it seems like the patch to install rust doesn't work

[yunchu]

change rust toolcahin setup action.
verified: https://github.com/openvinotoolkit/training_extensions/actions/runs/6400454287

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (0700999) 81.51% compared to head (9916bad) 81.51%.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #2505   +/-   ##
========================================
  Coverage    81.51%   81.51%           
========================================
  Files          516      516           
  Lines        38255    38255           
========================================
+ Hits         31184    31185    +1     
+ Misses        7071     7070    -1     

Flag	Coverage Δ
py310	81.51% <ø> (+<0.01%)	⬆️
py38	81.48% <ø> (ø)
py39	81.49% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sovrasov]

change rust toolcahin setup action. verified: https://github.com/openvinotoolkit/training_extensions/actions/runs/6400454287

Thanks!

[sovrasov]

@goodsong81 can we use develop version of Datumaro till the next pypi package is released? Since we already have 1.5 release branch, we could use develop for more extensive testing of the new OV. If the answer is yes, we can merge this PR soon

[goodsong81]

@goodsong81 can we use develop version of Datumaro till the next pypi package is released? Since we already have 1.5 release branch, we could use develop for more extensive testing of the new OV. If the answer is yes, we can merge this PR soon

I think so. Let's go ahead :)
BTW, @yunchu are we going to keep tookchain or it's just temporary for building datumaro from source distribution?
We might not want to guide OTX users to setup them to use the latest OTX develop branch.

[sovrasov]

E2E: https://github.com/openvinotoolkit/training_extensions/actions/runs/6420583996

[yunchu]

@sovrasov @goodsong81 I think it shouldn't be merged to any branches on the OTX. instead, datumaro 1.5.1rc1 should be published with upgrade version of OV

[yunchu]

applied datuamro version 1.5.1rc1

[yunchu]

@sovrasov datumaro version was updated to 1.6.0rc0

[sovrasov]

E2E: https://github.com/openvinotoolkit/training_extensions/actions/runs/6576792946

[sovrasov]

E2E passed