Add support for binding Memory and ReadOnlyMemory

[joelverhagen]

• I've read the guidelines for contributing and seen the walkthrough
• I've posted a comment on an issue with a detailed description of how I am planning to contribute and got approval from a member of the team
  • Feel free to close the PR if this change is not desired.
• The code builds and tests pass locally (also verified by our automated build checks)
• Commit messages follow this format:

        Summary of the changes
        - Detail 1
        - Detail 2

        Fixes #bugnumber

• Fixes Support Memory and ReadOnlyMemory parameter binding in Microsoft.Data.Sqlite #37484
• Tests for the changes have been added (for bug fixes / features)
• Code follows the same patterns and style as existing code in this repo

[Copilot]

Pull request overview

This PR adds support for binding Memory<byte> and ReadOnlyMemory<byte> types as SQLite parameters, addressing issue #37484. The implementation allows these modern memory types to be used interchangeably with byte arrays when binding parameter values.

Changes:

• Extended SqliteValueBinder.Bind() method to handle Memory<byte> and ReadOnlyMemory<byte> by extracting their spans
• Added type mappings for both memory types to SqliteType.Blob in the type mapping dictionary
• Added comprehensive tests for both memory types, including slice operations and type inference

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/Microsoft.Data.Sqlite.Core/SqliteValueBinder.cs	Added binding logic for Memory and ReadOnlyMemory types, plus type mappings to SqliteType.Blob
test/Microsoft.Data.Sqlite.Tests/SqliteParameterTest.cs	Added functional tests for Memory and ReadOnlyMemory binding with slice operations, plus type inference tests

[roji]

Thanks, LGTM!