feat: add new cache_query_by_user key

[eschutho]

SUMMARY

We'd like to use this feature from #20114 for the use case where someone doesn't have user impersonation on for the database, but still wants to create different cache keys in Superset for each user. I believe that some users prefer to use their database for RLS, but this will enable them to use the Superset RLS instead.

I thought about adapting with the existing key, but I didn't want to change any functionality, so instead I created a new key CACHE_QUERY_BY_USER

TESTING INSTRUCTIONS

With the CACHE_QUERY_BY_USER flag on, run a query with two different users, with different superset rls permissions and you should get different cached results.

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

[codecov]

Codecov Report

Merging #23415 (4a8c256) into master (42e8d1b) will increase coverage by 1.65%.
The diff coverage is 100.00%.

❗ Current head 4a8c256 differs from pull request most recent head c47e3c5. Consider uploading reports for the commit c47e3c5 to get more accurate results

@@            Coverage Diff             @@
##           master   #23415      +/-   ##
==========================================
+ Coverage   65.96%   67.61%   +1.65%     
==========================================
  Files        1907     1907              
  Lines       73590    73594       +4     
  Branches     7982     7982              
==========================================
+ Hits        48546    49763    +1217     
+ Misses      22996    21783    -1213     
  Partials     2048     2048              

Flag	Coverage Δ
hive	52.74% <37.50%> (-0.01%)	⬇️
mysql	78.40% <37.50%> (-0.01%)	⬇️
postgres	78.49% <37.50%> (-0.01%)	⬇️
presto	52.67% <37.50%> (-0.01%)	⬇️
python	82.33% <100.00%> (+3.41%)	⬆️
sqlite	76.96% <37.50%> (?)
unit	52.58% <100.00%> (?)

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

Impacted Files	Coverage Δ
superset/config.py	91.78% <ø> (ø)
superset/common/query_object.py	95.97% <100.00%> (+1.62%)	⬆️

... and 89 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[betodealmeida]

Looks great! I left a few small nits, but this is good to go.