[Bug] Pod stuck at FailedMount state

### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

### Search before asking

- [x] I have searched in the [issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no similar issues.

### Describe the bug

A pod may stuck at FailedMount indefinitely.

If a driver pod is created but the config map is not created, the driver pod gets stuck at FailedMount state indefinitely.

This seems to happen when kyuubi-server crashes after creating a driver pod but before config map is mounted.

This was observed in 1.10.3.

### Affects Version(s)

1.10.3

### Kyuubi Server Log Output

```logtalk

```

### Kyuubi Engine Log Output

```logtalk

```

### Kyuubi Server Configurations

```yaml

```

### Kyuubi Engine Configurations

```yaml

```

### Additional context

_No response_

### Are you willing to submit PR?

- [x] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix.
- [ ] No. I cannot submit a PR at this time.

Start by reproducing the driver-pod lifecycle described in the issue: create the pod, omit the config map, and simulate a Kyuubi server crash before mounting it. Trace the Kyuubi server and Kubernetes handling of that failure path; done means a driver pod is not left in FailedMount indefinitely when the config map is missing.

Written by the indexing model from the issue text.