[FEATURE] Make the operation/session/engine idle timeout configurable at client side.

### 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 feature

The idle timeout settings can only work if they are defined in the kyuubi-default. It is better to make them cnfigurable at client side, so that different sessions/engines/operations can have different timeout settings.

If this is not achievable, we should at least update the docs to tell users the limitations.

### Motivation

_No response_

### Describe the solution

_No response_

### Additional context

_No response_

### Are you willing to submit PR?

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

No files, tests, or entry points are named. Start by locating the existing kyuubi-default idle-timeout settings and the client configuration paths for operations, sessions, and engines. Done means establishing whether separate client-side timeouts are supported; otherwise, document the limitation clearly.

Written by the indexing model from the issue text.