feat(db_engine): Implement user impersonation support for StarRocks

[Woellchen]

SUMMARY

This PR adds user impersonation support for the StarRocks database by leveraging the native EXECUTE AS {user} WITH NO REVERT user management query.

TESTING INSTRUCTIONS

1. If necessary create a separate user on your StarRocks DB and your Superset instance. The names must match and it should be different from the user that is used for the StarRocks connection itself
2. Enable the user impersonation feature in the security settings of your StarRocks database
3. Log in to Superset with your testing user
4. Execute SELECT CURRENT_USER(); and see that it shows your current Superset user
5. Disable user impersonation feature again
6. Execute SELECT CURRENT_USER(); again and see that it changed back to the user of the StarRocks connection

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[github-actions]

Congrats on making your first PR and thank you for contributing to Superset! 🎉 ❤️

We hope to see you in our Slack community too! Not signed up? Use our Slack App to self-register.

[john-bodley]

Thanks @Woellchen for the change. Would you mind adding unit/integration tests to help ensure we don't have future regressions?

[Woellchen]

Thanks @john-bodley! Sure, I will look into it :)

[rusackas]

Looks like the pre-commit hooks also need to be run to make the linters happy.

[Woellchen]

Hey @rusackas and @john-bodley, I have tried to address your comments. Could you please another look at it? :)

[rusackas]

Running CI... fingers crossed!

[villebro]

@Woellchen can you rebase the PR to restart CI?

[villebro]

LGTM, but we need to rebase the PR to ensure tests are running ok on the other dbs due to the sig changes. Please ping me for a new review once done.

[tooptoop4]

@Woellchen can u pls add postgres + redshift? https://docs.aws.amazon.com/redshift/latest/dg/r_SET_SESSION_AUTHORIZATION.html , https://www.postgresql.org/docs/current/sql-set-session-authorization.html

[Woellchen]

Hey @villebro! I have rebased the branch and verified that everything still works as expected :) Thank you

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.65%. Comparing base (76d897e) to head (4147eeb).
Report is 688 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #28110       +/-   ##
===========================================
+ Coverage   60.48%   83.65%   +23.16%     
===========================================
  Files        1931      529     -1402     
  Lines       76236    38312    -37924     
  Branches     8568        0     -8568     
===========================================
- Hits        46114    32051    -14063     
+ Misses      28017     6261    -21756     
+ Partials     2105        0     -2105     

Flag	Coverage Δ
hive	48.86% <53.84%> (-0.30%)	⬇️
javascript	?
mysql	76.66% <53.84%> (?)
postgres	76.73% <53.84%> (?)
presto	53.41% <53.84%> (-0.39%)	⬇️
python	83.65% <100.00%> (+20.16%)	⬆️
sqlite	76.19% <53.84%> (?)
unit	60.40% <100.00%> (+2.78%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[Woellchen]

I had missed one usage for databricks, I fixed that now

[villebro]

LGTM, thanks for the patience and apologies for the loooong review process, excited to see this finally get merged! 🚀

[Woellchen]

No problem, glad we merged it! Thank you too!