Store resulting embedding from AI into local k/v for later lookup

Problem/Motivation

In Search API, each facet/filter/sort etc request prompts another search, which causes another text input embedding generation to happen. This is costly and not performant.

Proposed resolution

Create a local table that stores id, text, and vector at a minimum. In the event subscriber, look up the keys and return the vector if there is a record found. Otherwise, generate and store the vector result so it is then available in future searches.

Data model changes

Introduce table/schema.