This PR adds support for IDictionary<string, object> parameters to Update data expressions, bringing them in line with the existing Insert data expression functionality.

Problem

Previously, Update expressions only accepted anonymous objects for Set and Where operations:

// This worked, but required compile-time knowledge of column names
Update.Table("Users")
    .Set(new { Name = "Updated Name", Status = "Active" })
    .Where(new { Id = 123 });

However, Insert expressions already supported both anonymous objects and IDictionary:

// Insert supported both approaches
Insert.IntoTable("Users").Row(new { Name = "Test" });  // Anonymous object
Insert.IntoTable("Users").Row(new Dictionary<string, object> { ["Name"] = "Test" });  // IDictionary

This inconsistency made it impossible to build dynamic Update statements where column names and values are determined at runtime.

Solution

This PR adds IDictionary overloads to the Update expression interfaces and implementation:

// NEW: Now both approaches work for Update too
Update.Table("Users")
    .Set(new Dictionary<string, object> 
    {
        ["Name"] = "Updated Name",
        ["Status"] = "Active",
        ["LastModified"] = DateTime.Now
    })
    .Where(new Dictionary<string, object>
    {
        ["Id"] = 123,
        ["TenantId"] = "tenant-456"
    });

Changes Made

1. Enhanced ExpressionBuilderBase.GetData - Added support for IDictionary<string, object> input directly
2. Extended interfaces - Added IDictionary overloads to IUpdateSetSyntax and IUpdateWhereSyntax
3. Updated implementation - Added corresponding methods to UpdateDataExpressionBuilder
4. Comprehensive tests - Added full test coverage for new functionality and backward compatibility

Benefits

• Dynamic Updates: Enables building Update statements where column names/values are determined at runtime
• Generic Migrations: Allows creating reusable migration classes that work with any table/columns
• API Consistency: Update now works the same way as Insert regarding parameter types
• Backward Compatible: All existing code using anonymous objects continues to work unchanged
• Bonus: Delete and other data expressions automatically gained IDictionary support through the shared GetData method

Testing

All changes are thoroughly tested with both new IDictionary functionality and existing anonymous object usage to ensure no regressions.

Fixes #981.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.