Input/Output Binding Direction Issues

For some binding types (e.g. Bot DirectLineClient, NotificationHubClient, etc.) we have created separate input bindings in the templates, but from a runtime point of view the direction doesn't really matter. E.g. I suspect that NH client binding would work in C# regardless of what the selected direction is.

Furthermore, some of these bindings would actually fail in certain languages - etc. the above client bindings will only work in C#/F#, not Powershell etc. I bet things just blow up if you try that.

We should investigate all this and see if there are any validations we can put in place to make the behavior and error modes consistent across bindings.

Start by inventorying the input bindings in the templates, focusing on Bot DirectLineClient and NotificationHubClient, then trace how the runtime handles their direction and language support. Compare behavior across C#, F#, and PowerShell; done means documented validation rules and consistent behavior and error modes for all affected bindings.

Written by the indexing model from the issue text.