Fix awaitable response type comparison in async pipelines

[wassim-k]

Hi @hasanxdev,

I noticed another minor issue where if a pipeline behavior handles Task response type, the registrator still tries to register it against a request handler with ValueTask response type and vice versa, causing an exception "parameter constraint violation"

I've also added an extra test for request handler with IAsyncEnumerable return type to achieve 100% code coverage.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[hasanxdev]

@wassim-k Thank you so much! It seems this issue exists. I’ll look into it and get back to this PR.

[wassim-k]

This interface was added here to achieve 100% code coverage when searching for a matching pipeline interface:

pipeline.GetInterfaces().First(inter =>
    inter.IsGenericType && // <=== This branch when `false`
    inter.GetGenericTypeDefinition() == behaviorType).GenericTypeArguments[1]

[hasanxdev]

@wassim-k Thank you for your great contributions to the development of this library.
Your changes have been merged ❤️