feat: add extra column to tables and sql_metrics

[etr2460]

SUMMARY

Adds the columns mentioned in #10591 for extra metadata around tables and metrics (with certification being the first use case)

I'm PRing out only the migration first to ensure push safety with future code that references these columns.

TEST PLAN

CI, run the migration and see it succeed

ADDITIONAL INFORMATION

• Has associated issue:
• Changes UI
• Requires DB Migration.
• Confirm DB Migration upgrade and downgrade tested.
• Introduces new feature or API
• Removes existing feature or API

to: @john-bodley @graceguo-supercat @ktmud

[john-bodley]

@etr2460 do you think it would be advisable to add a note to UPDATING.md given this PR includes a migration?

[etr2460]

do you think it would be advisable to add a note to UPDATING.md given this PR includes a migration?

Do you think it matters? It should be completely push safe. Unless you think there'll be performance issues

[john-bodley]

@etr2460 reading through UPDATING.md I guess we only called out PRs that added columns which could be problematic like #8867. I guess the question is whether locking these tables will be problematic under production load. Note for MySQL adding a new column actually recreates the table and copies the data and the tables and sql_metrics tables could be sizable (though not as large as the logs or query table).

[codecov-commenter]

Codecov Report

Merging #10592 into master will decrease coverage by 4.71%.
The diff coverage is 8.33%.

@@            Coverage Diff             @@
##           master   #10592      +/-   ##
==========================================
- Coverage   63.98%   59.26%   -4.72%     
==========================================
  Files         768      356     -412     
  Lines       36359    22908   -13451     
  Branches     3431        0    -3431     
==========================================
- Hits        23264    13577    -9687     
+ Misses      12982     9331    -3651     
+ Partials      113        0     -113     

Flag	Coverage Δ
#cypress	?
#javascript	?
#python	59.26% <8.33%> (-0.46%)	⬇️

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

Impacted Files	Coverage Δ
...347acb39_add_extra_column_to_tables_and_metrics.py	0.00% <0.00%> (ø)
superset/tasks/slack_util.py	89.47% <100.00%> (ø)
superset/views/database/mixins.py	59.64% <0.00%> (-22.81%)	⬇️
superset/db_engine_specs/mysql.py	79.16% <0.00%> (-12.50%)	⬇️
superset/db_engine_specs/presto.py	70.56% <0.00%> (-12.14%)	⬇️
superset/views/database/validators.py	78.94% <0.00%> (-5.27%)	⬇️
superset/examples/world_bank.py	97.10% <0.00%> (-2.90%)	⬇️
superset/databases/api.py	85.18% <0.00%> (-2.78%)	⬇️
superset/examples/birth_names.py	97.36% <0.00%> (-2.64%)	⬇️
superset/db_engine_specs/postgres.py	97.43% <0.00%> (-2.57%)	⬇️
... and 423 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8fb304d...c8925e5. Read the comment docs.

[etr2460]

needed to pass CI