* add metabase commercial license to embedding-sdk

* attach commercial license file to npm package

* refactor license file generation

preliminary work for https://github.com/metabase/metabase/pull/41614

* Missing sentence for NQA documentation

* Add a test for optional field filter parsing

* Add Embedding SDK readme

* Update enterprise/frontend/src/embedding-sdk/docs/README.md

Co-authored-by: Nicolò Pretto <info@npretto.com>

* Update enterprise/frontend/src/embedding-sdk/docs/README.md

Co-authored-by: Phoomparin Mano <poom@metabase.com>

* Update enterprise/frontend/src/embedding-sdk/docs/README.md

Co-authored-by: Phoomparin Mano <poom@metabase.com>

* Clarify the result from `useQuestionSearch`

* Remove the mentioning of API key

Since we want to drop API key support for embedding SDK

* Add more detail

* Update enterprise/frontend/src/embedding-sdk/docs/README.md

Co-authored-by: Oisin Coveney <oisin@metabase.com>

* Update enterprise/frontend/src/embedding-sdk/docs/README.md

Co-authored-by: Phoomparin Mano <poom@metabase.com>

* Update enterprise/frontend/src/embedding-sdk/docs/README.md

Co-authored-by: Oisin Coveney <oisin@metabase.com>

* Update enterprise/frontend/src/embedding-sdk/docs/README.md

Co-authored-by: Oisin Coveney <oisin@metabase.com>

* Update enterprise/frontend/src/embedding-sdk/docs/README.md

Co-authored-by: Phoomparin Mano <poom@metabase.com>

* Update enterprise/frontend/src/embedding-sdk/docs/README.md

Co-authored-by: Oisin Coveney <oisin@metabase.com>

* Remove private GH repo

* Remove the compatibility table until we've made the first release

* Fix typo

* Add details how to run with locally built SDK

* Correct Metabase Embedding SDK case

* Make the instruction more concise

* Add a disclaimer

* Update config removing deleted property

* Add Oisin suggestion that was missed from rebasing

* Clarify plugin section

* Tweak SDK Readme

* Polish the limitation section

* Update the code sample into 4 sections making it easier to read

* Tweak overview and features section of README

* Add metabase configuration section

* Clean up section

* Replace the doc in the root embedding SDK directory

* Some tweaks and improvements to SDK README

* Tweaks to SDK README: wording, change flow, add section on running MB from master

* Update enterprise/frontend/src/embedding-sdk/README.md

Co-authored-by: Oisin Coveney <oisin@metabase.com>

* Feedback section

* Add simple InteractiveQuestion example

* SDK README: Tweak Slack wording

* Standardize fullstops + fix typo

* Clean up formatting

---------

Co-authored-by: Nicolò Pretto <info@npretto.com>
Co-authored-by: Phoomparin Mano <poom@metabase.com>
Co-authored-by: Oisin Coveney <oisin@metabase.com>
Co-authored-by: Alberto Perdomo <alberto.perdomo@gmail.com>

Co-authored-by: Emmad Usmani <emmadusmani@berkeley.edu>
Co-authored-by: Adam James <adam.vermeer2@gmail.com>
Co-authored-by: Mark Bastian <markbastian@gmail.com>
Co-authored-by: Jesse Devaney <22608765+JesseSDevaney@users.noreply.github.com>
Co-authored-by: Anton Kulyk <kuliks.anton@gmail.com>

* Add `collection.effective_ancestors` to search

Fixes #41909

The ultimate goal here is to be able to display a UI that showed the entire (effective) path to each collection.

This was a bit more painful than I'd hoped. The primary issue is that we
tied two things together:

- scoring results

- "serializing" results (really, partially serializing results, because
we do more work to shape the data later)

Why is this a problem? The `top-scorers` function took a transducer and
returned the *serialized* top scorers. Later, when we need to operate
on *all* the top results (in this case, to collect all the collection
IDs and names that we know of), we're looking at the serialized results.

In our case, we needed some data (collection location) that wasn't
included after serialization. We could add it, of course, but it's
frustrating to need to change the API of what data is *returned* from
the endpoint for purely internal purposes (changing the data available
during *processing*).

I ended up pulling serialization out of the scoring function. At some
point down the road, we should go ahead and move the `serialize`
function out of the `search.scoring` namespace entirely - there's really
no reason for it to belong there as far as I can tell.

* remove popular items entity

* support secondary icons

* remove defunct form components

* fix lil type errros

* add entity agnostic getIcon function

* remove recent items entity

* fix tests and support secondary icon

* fix display name

* prioritize recent items, do not filter search results

* fixing unit test

* temp

* rework DatasetFieldMetadataSidebar to use new form components

* temp

* removing unneeded import

* fixing display name form field

* temp

* more temp

* onChange for form elements

* e2e adjustment

* Button

* Reset button

* Skip failing unit test

* Fixes after merge

The new expressions `:month-name`, `:quarter-name` and `:day-name`
return the (user localized) names for these units, given the
corresponding number.

For example, 4 yields `"Apr"`, `"Q4"` or `"Wednesday"` respectively.

The `column-extract` drill uses these new expressions, rather than
generating its own `:case` clauses for them.

Note that `:day-of-week` and `:month-of-year` are tricky cases for i18n, but there are tests that exercise them thoroughly.

Part of the follow-up for Extract Column epic #38964.

* Add subTitle to ClickActions

* Add examples to column extractions

* Add test for examples

* Add test for examples

* Use rem helper

* Use JSDoc for todo

* Disambiguate between ColumnExtraction and ColumnExtractionInfo

* Update type of getExample

* Use rem helper

* Remove the custom resize handle

* Increase the handle width

* Notebook combine columns (#41379)

* Add CombineColumns dialog component

* Add combine columns to the expression editor widget

* Add placeholder for empty and space to the input

* Drop the first separator

* Remove empty string from eventual concat

* Add example to Combine Colunmns builder

* Show example in monospace

* Do not collapse spaces in example

* Use monospace in separator input

* Reorganise column flatten helper

* Add back button on combine buttons modal

* Select text when focussing separator input

* Add minimum height to example

* Use that same separator as the last row

* Use ExpressionWidgetHeader instead of hand-rolled header

* Fix type when generating example

* Correctly update default separator when a url column gets set

* Swap url and email checks

* Move column input into separate component

* Use QuerySelector for column select

* WIP: customise dropdown

* Export Input

* Use a button to render the column selector

* Add combine icon

* Use shortcut suggestion shortcut for combine columns

* Allow interacting with buttons inside the popover

* Use longDisplayName for button label

* Add asReturned

* Use asReturned in CombineColumns modal

* Make faux-select button styles match normal input

* Return focus to button when select closes

* Fix type of focus event

* Move ColumnInput component to a separate file

* Only show combine column shortcut on custom column

* Add missing test ids

* Add e2e test for combine column shortcut

* Remove white fill from paths

* Add color to combine icon

* Use function expression, not declaration

* Remove comment

* Move initial default separator to constant

* Remove unused select option helpers

* Add isInteger helper to Lib

* Add case for integer columns

* Add unit tests for util

* Add SuggestionShortcut type to props for Suggestions

* Remove {enter} which broke test

* Do not use !important

* Simplify classname into object-style

Co-authored-by: Uladzimir Havenchyk <125459446+uladzimirdev@users.noreply.github.com>

* Use direct override on Button instead of class

* Fix formatting issue

* Use .select() to select input

* Avoid selecting placeholder text

* Avoid losing focus when window loses focus

* Rename evt to event

* Add monospace variant to Text

* Use monospace variant in Example

* Use monospace font from theme

* Match faux-select label styles to our TextInput label styles

* Remove empty default variant

* Add limit to the test case

* Remove unnecessary within wrapper

* Use rem

Co-authored-by: Nemanja Glumac <31325167+nemanjaglumac@users.noreply.github.com>

---------

Co-authored-by: Uladzimir Havenchyk <125459446+uladzimirdev@users.noreply.github.com>
Co-authored-by: Nemanja Glumac <31325167+nemanjaglumac@users.noreply.github.com>

* Remove intercept we're not waiting for

* Use have.text instead of contain

* Use cy.button

* Expand cancel test

* Remove duplicate title

---------

Co-authored-by: Uladzimir Havenchyk <125459446+uladzimirdev@users.noreply.github.com>
Co-authored-by: Nemanja Glumac <31325167+nemanjaglumac@users.noreply.github.com>

* Re-write E2E repro for 39221

* Convert to TS

Bumps [mysql2](https://github.com/sidorares/node-mysql2) from 3.9.4 to 3.9.7.
- [Release notes](https://github.com/sidorares/node-mysql2/releases)
- [Changelog](https://github.com/sidorares/node-mysql2/blob/master/Changelog.md)
- [Commits](https://github.com/sidorares/node-mysql2/compare/v3.9.4...v3.9.7

)

---
updated-dependencies:
- dependency-name: mysql2
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: Chris Truter <chris@metabase.com>

* Fix the flake in add-required-filter-if-needed-test due to field order

* /s/oredered-filter/ordered-filter

Column extractions are "canned" expressions based on a column's
type. For example, we might extract the weekday from a temporal column,
or the domain from an email or URL column.

This logic already existed inside the `column-extract` drill; this pulls
it out as a top-level concept, since extractions are also being
integrated into the notebook editor apart from drills.

Part of the follow-up for Extract Column epic #38964.