* Enable repro

* Move saved questions virtual DB id to own file

* Add saved question helpers

* Add test-id to Metabase logo component

* Extend repro test to cover archived items handling

* Handle saved question actions in schema entity

* Handle saved question actions in table entity

* Fix moved file import

* Fix Cypress can't find logo in EE (whitelabeling)

* Fix saved questions order

* Fix saved questions included in database tables

* Remove not used prop

* Make CollectionSidebar a functional component

* Fix accidentaly closing some collections

* Static viz: respect custom X and Y axis labels

* Static viz: allow rendering non-timeseries line charts

* Test fixes 

Change implementation of docsUrl to handle RC suffixes for EE versions

Change the regex used to test the tag to detect any OSS or EE version, including (possibly) an arbitrary suffix after the major and minor parts, and normalize to the major OSS equivalent version instead.  If the suffix, OTOH, is `-SNAPSHOT` (ignoring case), then the doc tag will be `latest`, on the theory that this is as local development build.

v0.41.0 => v0.41
v1.41.1 => v0.41
v1.41.2-RC1 => v0.41
v1.42.0-SNAPSHOT => latest

Adding unit tests for all cases

Update behavior so that -SNAPSHOT suffix points to "latest"

#18148 Repro: "Save" button shouldn't appear before one selects the source for a native question (#18259)

* Add `setupSMTP` helper function

* Remove deprecated `setupDummySMTP` helper

* Re-use `setupSMTP` helper in tests

* Always clear Webmail's inbox after setting up the SMTP

Previous PRs for error cards page were laser focused on getting everything to work, as opposed to actually conforming to spec. This one gets it closer to spec, although product wants reloading animations which are not there yet. To wit,

- Indicates to end user what the current running state is. Given the many orders of magnitude in DB query run times I think something robust and non-ephemeral is necessary here (looking at some sort of expanded QE model) but Maz suggested expedient method and I took it
- No more left nav on the table page
- Page heading for table page
- Independent scroll-x behavior on the table
- Styling for the error section on the table page
- Select-all component. Note that the interaction behavior with pagination is fiddly. (but less fiddly now that it's all based on card id's instead of row numbers)
- Coalescing default behavior for Our Analytics collection (default collection) and null number of dashboards
Rename error name to error content search

* Fix virtual fields are missing in ParameterValueWidget

* fix fk filter parameters

Remove the `driver/format-custom-field-name` implementation for :snowflake, which was causing the problem and appears to be no longer needed anyway

Add test for this scenario to `metabase.query-processor-test.expression-aggregations-test`

* Fix Dashboard Subscription email validation (second pass)

* Always validate Pulse channels in test endpoint

* Update Link component's code style

* Add disabled style to Link

* Disable "Save" button when can't run query

* Animate Link color and opacity changes

* restyle the Verify button

* remove unused components

* make the verify button blue

Fix cache native queries not working (underlying problem is unit conversion actually) (18160) (#18230)

Cache TTL is defined in the nice new column things as per hour. The actual cache wanted it in seconds. There wasn't a conversion hours->secs before, which was the underlying illusion that gave rise to #18160 - with a properly set cache ttl the cache works fine. But the cache ttl's weren't getting set to proper values because of that lack of unit conversion. So here's the conversion, hours->secs.

* Make webpack output closer to webpack 4 and fix whitelabelling

* Fix recently-viewed.cy.spec.js

Not sure why it's started failing with this PR, but adding wait for text.

When all the necessary data hasn't been fetched you can find yourself in
stuck in a loop between the invalid state checks in DataSelector's
componentDidUpdate method and the skipSteps method.

1. there seems to always be a single schema (the "Everything Else"
   schema) available on instantiation
2. the skipSteps method auto-selects this schema when no other schemas
   exist
3. there's some pre-existing logic to avoid getting in this loop by
   checking the is_saved_questions property of the database in the
   selectedSchema. However, for whatever reason this property doesn't
   exist until AFTER we've fetched some things.

The fix is checking a property that is guaranteed to exist, the ID for
the "Everything Else" database