Add unit test for ElicitAsync<T> with no SerializationOptions #798

[mehrandvd]

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[eiriktsarpalis]

I'm not sure why adding such a test is necessary. The behavior of McpJsonUtilities.DefaultOptions which is what backs this (and other methods) serialization behavior is something that we're already testing for.

[mehrandvd]

OK, so I'm closing this issue.

[eiriktsarpalis]

Thanks