EFCore SQL Server provider maps a SerializedMetadata column that doesn’t exist

What happened?
After splitting out Elsa.Extensions into its own repo, the SQL-Server EF Core model for ActivityExecutionRecord was extended to include a SerializedMetadata column. But our existing database schema hasn’t been updated, so every upsert now fails with:

Invalid column name 'SerializedMetadata'.

Why it’s a problem:
Users who cannot or do not want to immediately run a database migration are completely blocked—no activity records can be written or updated.

Environment:

Elsa.Core version: latest fork

Elsa.Persistence.EFCore.SqlServer version: latest fork

Start by reproducing an ActivityExecutionRecord upsert against the existing SQL Server schema and compare it with the EF Core model that includes SerializedMetadata. Determine the expected compatibility behavior for databases without that column; done means activity records can be written and updated without the invalid-column failure.

Written by the indexing model from the issue text.