fix(ci): remove faiss metadata_store from auth workflow to fix table creation race

The faiss provider's metadata_store config (using sql_default) caused its
initialize() to trigger _ensure_engine() via a fetch_all before the
responses provider had registered its table metadata. Since all sql_default
stores share a single SqlAlchemySqlStoreImpl, metadata.create_all() ran
without the responses table, and the lazy _ensure_engine() guard
(if self._engine is not None: return) prevented it from ever being created.

Removing metadata_store from faiss (matching the passing branch config)
ensures no provider triggers _ensure_engine() before all tables are
registered. The vector store access control tests still work through the
routing table ABAC layer (vector_store::*).

Verified locally: responses table created successfully, vector store
CRUD operations work.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Francisco Javier Arceo <farceo@redhat.com>

Author: franciscojavierarceo

.github/workflows/integration-responses-conversations-auth-tests.yml

@@ -132,9 +132,6 @@ jobs:
                   persistence:
                     namespace: vector_io::faiss
                     backend: kv_default
-                  metadata_store:
-                    table_name: vector_store_metadata
-                    backend: sql_default
             tool_runtime:
               - provider_id: file-search
                 provider_type: inline::file-search
@@ -170,9 +167,6 @@ jobs:
               prompts:
                 table_name: prompts
                 backend: sql_default
-              vector_stores:
-                table_name: vector_store_metadata
-                backend: sql_default
           models:
           - model_id: openai/gpt-4o
             model_type: llm