`configure`: Error in detecting CUDA toolkit path
Hi @sorousherafat ,

Could you please confirm the steps you followed to install cuda toolkit ?

Thank you! Hello,

It was just a simple

```bash
sudo apt install nvidia-cuda-toolkit
```

Thanks in advance. @DEKHTIARJonathan , Could you please take a look into this, this seems to be related with CUDA toolkit path. Thanks! Confirmed on Debian 12.

> Tensorflow 2.15
Debian 12
Python 3.11
Bazel 4.2.3
GCC 12.2
Cuda 11.8
CuDNN 8.5

It looks like a similar [issue](https://github.com/tensorflow/tensorflow/pull/21499) was fixed six years ago, so maybe this is a regression.
### Issue type

Build/Install

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

Yes

### Source

source

### TensorFlow version

3b205a3

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 23.04

### Python version

3.11

### Bazel version

4.2.3

### GCC/compiler version

12.2.0

### CUDA/cuDNN version

11.8

### GPU model and memory

GTX 1050 Ti - 4 GB

### Current behavior?

I am trying to using `configure` script before building Tensorflow from source.

When I am trying to configure CUDA support using default list of base paths to look for CUDA libraries and headers, I get the following error:

```out
Inconsistent CUDA toolkit path: /usr vs /usr/lib
```

I have included the path of each tool in the next section.

I have tried different combinations for list of base paths and even changed `third_party/gpus/find_cuda_config.py` file to add default subdirectory paths but still get this error.

### Standalone code to reproduce the issue

Here's where everything is installed:

```bash
$ locate cuda.h
```

returns:

```out
/usr/include/cuda.h
```

and

```bash
$ which nvcc
```

returns:

```out
/usr/bin/nvcc
```

and

```bash
$ locate libcudart.so.11
```

returns:

```out
/usr/lib/x86_64-linux-gnu/libcudart.so.11.0
/usr/lib/x86_64-linux-gnu/libcudart.so.11.8.89
```

and

```bash
$ locate -r libdevice*.10.bc
```

returns:

```out
/usr/lib/nvidia-cuda-toolkit/libdevice/libdevice.10.bc
```

### Relevant log output

_No response_