fix: Monospacing errors in dashboards & charts

[codemaster08240328]

SUMMARY

On Charts and Dashboards, if the user has an error, the error message should be displayed in a monospace font so some of the formatting / details is not lost.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Before

After

TESTING INSTRUCTIONS

[codecov]

Codecov Report

Merging #18796 (683c265) into master (2d67d2f) will increase coverage by 0.00%.
The diff coverage is 100.00%.

❗ Current head 683c265 differs from pull request most recent head 93b3f7d. Consider uploading reports for the commit 93b3f7d to get more accurate results

@@           Coverage Diff           @@
##           master   #18796   +/-   ##
=======================================
  Coverage   66.32%   66.32%           
=======================================
  Files        1620     1620           
  Lines       63087    63089    +2     
  Branches     6372     6372           
=======================================
+ Hits        41840    41842    +2     
  Misses      19590    19590           
  Partials     1657     1657           

Flag	Coverage Δ
javascript	51.26% <100.00%> (+<0.01%)	⬆️

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

Impacted Files	Coverage Δ
superset-frontend/src/chart/Chart.jsx	53.44% <100.00%> (+1.66%)	⬆️

---

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 2d67d2f...93b3f7d. Read the comment docs.

[rusackas]

/testenv up

[github-actions]

@rusackas Ephemeral environment spinning up at http://54.185.22.55:8080. Credentials are admin/admin. Please allow several minutes for bootstrapping and startup.

[rusackas]

This has a side effect of monospacing ANY error in this dashboard/explore context. See screenshot below of one example.

@kasiazjc any objections to this? I think the pros outweigh the cons here.

[kasiazjc]

@rusackas does error always contain sql/code? If yes, I think that pros outweigh the cons if we cannot separate those. If no - this could create more confusion 🤔

[villebro]

Thanks for fixing this @codemaster08240328! This has been an annoyance for a long time, especially on BigQuery where error messages have been very difficult to decipher due to the type face being variable width.

@kasiazjc @rusackas due to the varied exception types we get from analytical databases it will often be difficult to distinguish between code-like exceptions that need monospacing and more general exceptions that don't. We can potentially add more fine-grained logic to the backend that tries to identify which messages need monospacing and which don't, but until we do I suggest merging this as-is, as I feel the problem this fixes is more severe than the side-effect it introduces.

[villebro]

nit: I would perhaps consider naming this MonospaceMessage

[github-actions]

Ephemeral environment shutdown and build artifacts deleted.