Add trigger binding support

[AmeyaRele]

No description provided.

[Charles-Gagnon]

Please add both unit and integration tests covering the functionality of this feature.

(also make sure you merge in latest from main and fix any build errors. We had to go back to netstandard2.0 from netstandard2.1 for bundle support which means some language features aren't available)

[dzsquared]

reminder: this PR needs to be retargeted to a feature branch for trigger support and not merged to main

edit: this is already in a feature branch

[Charles-Gagnon]

Still a few comments to take a look at but overall looks good enough to me.

Although I want there to be a lot more debug logging done in all the parts. I'm not seeing any in SqlTableChangeMonitor for example. In general here are the things I'll be looking for :

1. Message at the start of every task and sub task (Getting changes from table, Updating state tables, Getting list of changes, Got changed rows {....}) and so on. The goal should be to be able to tell exactly where something went wrong and what it was doing when an issue occurs, regardless of where that was.
2. Log queries executed and how long they took
3. Extra logging around any of the locking (include thread IDs if that isn't included by default)
4. Make sure all errors are logged with any extra information that may be helpful in determining cause of the error

@lucyzhang929 @MaddyDev Please help make sure that we get as complete of a logging story as we can - we want to have as much as we can now before we give this to customers.

Also we should make sure to get basic usage telemetry set up - we can get some amount of stuff from the AF folks but that won't include people running locally so it'd be good to make sure we have a complete story ourselves as well. I'll follow up separately on my thoughts for that to get started.

[JatinSanghvi]

Although I want there to be a lot more debug logging done in all the parts. I'm not seeing any in SqlTableChangeMonitor for example. In general here are the things I'll be looking for :

1. Message at the start of every task and sub task (Getting changes from table, Updating state tables, Getting list of changes, Got changed rows {....}) and so on. The goal should be to be able to tell exactly where something went wrong and what it was doing when an issue occurs, regardless of where that was.
2. Log queries executed and how long they took
3. Extra logging around any of the locking (include thread IDs if that isn't included by default)
4. Make sure all errors are logged with any extra information that may be helpful in determining cause of the error

Created #287 for this one.

[JatinSanghvi]

Closing this pull request as it need not be merged soon and need not be reviewed further. When the triggerbindings branch needs to be merged into main branch, it can be either merged directly or through a new PR.