Update omegaconf version to 2.3.0

[RyoYang]

Update omegaconf version to 2.3.0 as omegaconf 2.0.6 has a non-standard dependency specifier PyYAML>=5.1.*. pip 24.1 will enforce this behaviour change.
Discussion can be found at pypa/pip#12063

[codecov]

Codecov Report

Attention: Patch coverage is 93.75000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 85.78%. Comparing base (7435f10) to head (86138e2).

Files	Patch %	Lines
superbench/runner/runner.py	90.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #631      +/-   ##
==========================================
- Coverage   85.79%   85.78%   -0.02%     
==========================================
  Files          97       97              
  Lines        6915     6920       +5     
==========================================
+ Hits         5933     5936       +3     
- Misses        982      984       +2     

Flag	Coverage Δ
cpu-python3.6-unit-test	71.59% <93.75%> (-0.01%)	⬇️
cpu-python3.7-unit-test	71.59% <93.75%> (-0.01%)	⬇️
cpu-python3.8-unit-test	71.62% <93.75%> (-0.40%)	⬇️
cuda-unit-test	83.86% <93.75%> (-0.02%)	⬇️

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

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

[cp5555]

Strange to set the upper version

[yukirora]

Is this change compatible with the old pip like 22.0.1?

[RyoYang]

Is this change compatible with the old pip like 22.0.1?
It should be compatible, cpu-unit-test pipeline (Job python3.6) passed all ut and it used a lower version of pip 21.2.4.

[dong0321]

Seems to be the same issue. I am building release/0.10 with rocm6.0 dockerfile.

[dong0321]

@RyoYang could please check if this need to be fixed also in release/0.10

[dong0321]

Build successed after change to 2.3.0.