[INTEL oneDNN] Refactoring: replace/remove MKL ML API calls
@penpornk Hi Penporn, I noticed that there were failures related internal CI and AMD ROCm build. But I am not sure if this PR caused them. The old should NOT be executed in recent years after we moved from MKL ML to MKL DNN (around 2017 or 18). 
Please help to check. Thanks!

My next step is to clean up related bazel configuration (to get rid of "if_mkl_ml" staff).          -GZ @gzmkl I haven't seen the latest ROCm results on this PR. (It's still running at the time I'm writing this comment.) But ROCm has been having infra failure lately. (It failed in many other PRs.) So it's likely unrelated to this PR. I'll take a look again after it's done running. :) @penpornk  Please help to check the latest ROCm results on this PR. I could not find anything with the "Details" link.  THANKS This PR is replaced by the new one (hopefully no more conflicts after oneDNN 3.x integration)

https://github.com/tensorflow/tensorflow/pull/61471

Thus close this one

MKL ML has been replaced by MKL DNN and now oneDNN. It is not supported anymore. 
In TensorFlow, there are still some MKL calls even though related methods and tests are NOT called any more. 

The PR replaces and removes calls to MKL ML (cblas) APIs which are not supported long time ago.

1. For FP32 Matmul, oneDNN dnnl_gemm() will be called.
2. For FP64 Matmul, it will NOT be supported as oneDNN currently does not support it. 

NEXT STEP: clean up MKL ML related configuration (bazel files). 