fix(sqllab): prev shema/table options remained on fail

[justinpark]

SUMMARY

Due to the difference between the data of the RDK query and currentData, an issue occurred in SQL Lab where, instead of showing an empty selection due to (permission) errors, the schema and table selector allowed the selection of previous database or schema options.

  data?: T // The latest returned result regardless of hook arg, if present
  currentData?: T // The latest returned result for the current hook arg, if present

As a result, it was possible to combine schema and table selections that do not actually exist, causing errors and potentially confusing users.
This commit addresses these issues by changing to currentData, ensuring that only results existing in the strictly selected database and schema are displayed.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Before:

before--using-current-data.mov

After:

after--using-current-data.mov

TESTING INSTRUCTIONS

Select a db/schema/tables in Sql Lab page
Choose a db that doesn't allow to access the schemas
See the schema selection remained or not after db selection changed

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

[justinpark]

restore from this accidental removal

[sadpandajoe]

@supersetbot label 4.1

[justinpark]

@michael-s-molina Please add this hotfix on 4.0 too.