* question marks

* remove all question mark notes except about json

Fix - Invalid join clause does not disappear after changing query source to use a different database (#45025)

* Reset JoinDraft state on database change (fixes metabase#42385)

* Add repro for #42385

* Use admin user

* add default font family

* use metabase provider internal component for tests

* Add repro for #34350

* Reduce diff

* make ad-hoc changelog generation actually useful

* add github action

* remove test code

* fix whitespace

* fix formatting

Add a repro for 'Permission error before finishing referencing a question in the native query' (#44995)

* Create new release note sections

* add explanatory text

* return data about the proper billing status

* fix copy

* fix the tests

* support sorting on funnel bar charts

* fix funnel bar row display setting

* spec

* mark a defsetting as being :sensitive?

* add test

* Fix SDK components loaders

* Review fixes

* Add reproduction for #38989

* Use saveQuestion instead of clicking trough the UI

Co-authored-by: Kamil Mielnik <kamil@kamilmielnik.com>

* Use openOrdersTable instead of manually clicking through the ui

Co-authored-by: Kamil Mielnik <kamil@kamilmielnik.com>

* Create question programmatically in test

---------

Co-authored-by: Kamil Mielnik <kamil@kamilmielnik.com>

* Add a test table with many schemas

* Add a repro for #28106

* Format code

* Add issue tag

Repro #27521 - Query fails when selecting two fields from nested query, when fields are identical except for their join-alias (#44909)

* Add repro for #27521

* Improve assertions

* Add comments

* Use saveQuestion helper

* Use openOrdersTable helper

Add a reproduction for "Cannot find the new column in pick columns after alter schema and synced" (#44882)

* Add a reproduction for metabase#41765

* Navigate manually to the admin page

* Wrap non-latin characters in a span specifying working font

Fixes: #38753

CSSBox seems to have a bug where font fallback doesn't work properly. This is noticeable when a font does not contain
glyphs that are present in the string being rendered. For example, Lato does not have many international characters,
so the rendered version of tables (that show up in Slack messages) will not render properly, making the card
unreadable.

Since this appears to be a downstream bug, I've opted to work around this limitation by wrapping any non-latin
characters in a <span> that specifies the font family to be sans-serif, which should contain the glyphs to properly
render.

This leaves Lato in place for other characters.

For now, I figured it's worth trying this solution over using Noto for 2 reasons:
- we can keep Lato, which has been the decided font style for the app for some time (this keeps things consistent
where possible)
- the Noto font containing all glyphs is quite a large font (>20mb, I think) and it would be nice to avoid bundling
that if we can.

* stub installed fonts test

* typo

* Do wrapping, but now per-string, and in Clojure data not html string

I've decided that a reasonable solution is to still wrap strings containing non-lato characters. But it's not done
with str/replace to the html string but rather in a postwalk over the Hiccup data prior to rendering.

Seems like a decent compromise of issues without patching CSSBox or fixing upstream (may be good to do, but will take
longer to get a fix in).

* add test checking that glyphs render correctly

* Add a test that directly checks the wrapping fn

* Change the string to keep the linter quiet

* Change how we check if string can be rendered to faster method, new Lato Font

With Sanya's help, the way I check if a given string is renderable with Lato is now faster.

Also use the full Lato font, not just the 'latin' lato so we can cover more chars

* change lato so that it loads the fn even in a fresh test run

* improve cartesian charts performance

* drop unused import

Add a repro for 'Filter values in dropdown are not getting populated in SQL question based dashboard' (#44927)

* prevent pin maps from filtering out rows with null values

- since pin maps are just displaying where the data is by latitude and longitude, we do not need to filter the pin just because one of the rows is null.
- the metric column selection does not make sense for pins as they just represent that data through coordinates (no aggregations or values displayed), so we should not be filtering out any data just because it is null

* add unit test

fix(sdk): Fix SDK types, split files, and improve navigation within SDK `InteractiveQuestion` (#44898)

* Rather support old files, than duplicate columns

* Cope with driver specific failure modes

* Restore bytes comment