[Bug] Engine space should be ignore the version change

### 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/incubator-kyuubi/issues?q=is%3Aissue) and found no similar issues.

### Describe the bug

We use `${serverSpace}_${KYUUBI_VERSION}_${shareLevel}_${engineType}` as the parent path of the engine space, but during hot upgrade kyuubi cluster with different version, we will have two version of engine space. As a result, a user share level engine can be created again since there are two engine space at that monent.

```
Client A -> Kyuubi Instance 1.5.0 -> engine A
Client A -> Kyuubi Instance 1.5.1 -> engine B
```

### Affects Version(s)

master/1.5

### Kyuubi Server Log Output

_No response_

### Kyuubi Engine Log Output

_No response_

### Kyuubi Server Configurations

_No response_

### Kyuubi Engine Configurations

_No response_

### Additional context

_No response_

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

Start by tracing where the engine-space parent path is built from `${serverSpace}_${KYUUBI_VERSION}_${shareLevel}_${engineType}` and review how hot upgrades create engine spaces across Kyuubi versions. Reproduce the 1.5.0/1.5.1 scenario, then verify that a shared engine is not created twice solely because the server versions differ.

Written by the indexing model from the issue text.