Trino create client session should use engine seesion user

[lsm1]

🔍 Description

Issue References 🔗

In engine share level such as SERVER, KYUUBI_SESSION_USER_KEY is a fixed value, we should use the engine session user as the trino client session user

Describe Your Solution 🔧

Types of changes 🔖

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪

Behavior Without This Pull Request ⚰️

Behavior With This Pull Request 🎉

Related Unit Tests

---

Checklist 📝

• This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.22%. Comparing base (2c9fb3d) to head (4393183).
Report is 13 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #6120      +/-   ##
============================================
+ Coverage     61.12%   61.22%   +0.09%     
  Complexity       23       23              
============================================
  Files           623      623              
  Lines         37200    37485     +285     
  Branches       5040     5077      +37     
============================================
+ Hits          22738    22949     +211     
- Misses        12001    12075      +74     
  Partials       2461     2461              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[pan3793]

In engine share level such as SERVER, KYUUBI_SESSION_USER_KEY is a fixed value

this seems not an expected behavior, will take a look later

[pan3793]

The issue should be val sessionConf: KyuubiConf = sessionManager.getConf, it's actually an engine level conf, but we expect a session level conf.

[pan3793]

This issue should be fixed in an alternative approach #6148