Implement bypass deferred binding

[surgupta-msft]

Issue describing the changes in this PR

Resolves #1495

Design doc - Link

Implementation Summary

1. Binding Attributes are updated as per design doc - (Refer section: class design)

   • Binding Attributes updated - BlobInputAttribute, BlobTriggerAttribute, CosmosDBInputAttribute
   • Converters updated - BlobStorageConverter, CosmosDBConverter
   • New Attributes added - AllowConverterFallback, SupportedConverterTypes

     // Binding Attributes to advertise all the converters they support and enable/disable fallback to registered converters
     [AllowConverterFallback]        // Attribute indicates that fallback to default converters is enabled by BindingAttribute
     [InputConverter(typeof(MyConverter1))] // Attribute to indicate the converter supported by BindingAttribute 
     [InputConverter(typeof(MyConverter2))]
     class MyTriggerAttribute // or MyInputAttribute
     {   
     
     }
   
     // Converters to advertise the support for deferred binding and types that are supported
     [SupportsDeferredBinding]        // Attribute indicates that converter supports deferred binding
     [SupportedConverterTypes(typeof(MyType1))]  // Attribute to indicate the type supported by converter
     [SupportedConverterTypes(typeof(MyType2))]
     [SupportedConverterTypes(typeof(IEnumerable<MyType2>))]
     class MyConverter
     {
     
     }
     ```

2. Changes in Function Metadata Generator include -

   • Logic to correctly assign SupportsDeferredBinding by analyzing attributes advertised by BindingAttributes and Converters
   • Handling for cases such as POCOs, Collections - (Refer section: Metadata Generation flow)

3. Changes in GrpcFunctionDefinition.cs -

   • This class will cache information about Binding Attributes and Converters in PropertyBags during Function indexing time to avoid type evaluation during invocation time.
   • Information cached here -
     • Whether BindingAttribute supports fallback to registered converters
     • A Dictionary with Key as converter and value as Properties for that converter such as all the types supported by it and support for Json Deserializable objects.

4. Invocation flow - (Refer section: Invocation flow)

   • Changes in DefaultInputConversionFeature.cs
     • Get list of all the converters advertised by BindingAttribute and hence all the types supported by each converter.
     • Check if TargetType is supported by the converter before invoking it.
     • Check if Fallback to registered converters is enabled by Binding attribute. If yes. continue with default probing.

Pull request checklist

• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• I have added all required tests (Unit tests, E2E tests)

Additional information

Additional PR information

[kshyju]

Overall, looks good.

The PR title suggests that this change is to skip the new binding behavior (so things will work as hot it is today - populating binding data in host). But this PR has more changes than that (Ex: using converter types advertised by trigger, using supported types published by converter etc.) Consider updating title as needed.