Feature request: Sql trigger params

When triggering via SQL, it would be awesome if you could allow the columns in the trigger to be used in the input binding, like it is done with HTTP trigger params.

Example

```
{
"bindings": [
{
"name": "changes",
"type": "sqlTrigger",
"direction": "in",
"tableName": "[dbo].[Products]",
"params": ["Cost"]
"connectionStringSetting": "AzureSQLConnectionString"
},
{
"name": "products",
"type": "sql",
"direction": "in",
"commandText": "select * from Products where Cost = @Cost",
"commandType": "Text",
"parameters": "@Cost={cost}",
"connectionStringSetting": "SqlConnectionString"
}
]
}
```

The issue names SQL trigger and SQL input bindings but no files or tests. Start by tracing those binding entry points and comparing the requested column-parameter behavior with HTTP trigger parameters; done means trigger columns can populate parameters such as {cost} for the SQL query, with coverage for the example.

Written by the indexing model from the issue text.