OneDNN logs are not printing while building TF with --config=mkl_aarch64
@tilakrayal  I see the same issue when I tried compiling latest TFv2.13 from source on Graviton(ARM) with the latest CLANG 16 compiler and with --config=mkl_aarch64. The compilation goes through, but when we run some TF application, we are not able to see any OneDNN logs even with **export ONEDNN_VERBOSE=1** set. we are getting onednn_logs after setting two flags:

export ONEDNN_VERBOSE=1

export TF_ENABLE_ONEDNN_OPTS=1 Are you satisfied with the resolution of your issue?
<a href="https://docs.google.com/forms/d/e/1FAIpQLSfaP12TRhd9xSxjXZjcZFNXPGk4kc1-qMdv3gc6bEP90vY1ew/viewform?entry.85265664=Yes&entry.2137816233=https://github.com/tensorflow/tensorflow/issues/61376">Yes</a>
<a href="https://docs.google.com/forms/d/e/1FAIpQLSfaP12TRhd9xSxjXZjcZFNXPGk4kc1-qMdv3gc6bEP90vY1ew/viewform?entry.85265664=No&entry.2137816233=https://github.com/tensorflow/tensorflow/issues/61376">No</a>

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.13.0

### Custom code

Yes

### OS platform and distribution

Ubuntu 22.04.2 LTS

### Mobile device

_No response_

### Python version

3.10.6

### Bazel version

6.3

### GCC/compiler version

11.3.0

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

I am expecting OneDNN logs should print while running deep learning model such as resnet50, if we export ONEDNN_VERBOSE=1

### Standalone code to reproduce the issue

```shell
To reproduce same, we have to build TF on Arm CPU, and use following command to build:
bazel build --config=mkl_aarch64 //tensorflow/tools/pip_package:build_pip_package
```


### Relevant log output

_No response_