[submodule] Upgrade oneDNN to v2.0

[bartekkuncer]

This change upgrades oneDNN used by mxnet to v2.0.

[mxnet-bot]

Hey @bartekkuncer , Thanks for submitting the PR
All tests are already queued to run once. If tests fail, you can trigger one or more tests again with the following commands:

• To trigger all jobs: @mxnet-bot run ci [all]
• To trigger specific jobs: @mxnet-bot run ci [job1, job2]

---

CI supported jobs: [unix-cpu, sanity, clang, centos-cpu, miscellaneous, website, unix-gpu, windows-cpu, centos-gpu, edge, windows-gpu]

---

Note:
Only following 3 categories can trigger CI :PR Author, MXNet Committer, Jenkins Admin.
All CI tests must pass before the PR can be merged.

[bartekkuncer]

@mxnet-bot run ci [unix-cpu]

[mxnet-bot]

Jenkins CI successfully triggered : [unix-cpu]

[bartekkuncer]

@mxnet-bot run ci [unix-gpu, centos-gpu]

[mxnet-bot]

Jenkins CI successfully triggered : [unix-gpu, centos-gpu]

[bartekkuncer]

@mxnet-bot run ci [centos-gpu]

[mxnet-bot]

Jenkins CI successfully triggered : [centos-gpu]

[bartekkuncer]

@leezu @szha Please help with the merge. This change just upgrades oneDNN used by mxnet to v2.0.

[szha]

@leezu how does it impact horovod integration?

[leezu]

It breaks it. @bartekkuncer can you look at updating MXNet/Horovod to work with oneDNN v2? See horovod/horovod#2530 for reference

[bartekkuncer]

It breaks it. @bartekkuncer can you look at updating MXNet/Horovod to work with oneDNN v2? See horovod/horovod#2530 for reference

Sure, I will look into it.