Change wevbtt-azsearch-indexer from QueueTrigger to CosmosDBTrigger

[yokawasa]

Action

Changing wevbtt-azsearch-indexer function from QueueTrigger to CosmosDBTrigger

Purpose

• 1. It's much more straightforward to use CosmosDBTrigger than to use QueueTrigger in dealing with the data ingested into CosmosDB
• 2. To make initial configuration steps simpler, eliminate the storage queue that currently used by wevbtt-azsearch-indexer, QueueTrigger.

[yokawasa]

Decide not to go with CosmosDB Trigger for the following reasons:

• CosmosDB Trigger + CosmosDB Binding for in-direction doesn't work as expected from Python code (Further investigation is needed to find root cause)
• Queue Trigger + CosmosDB Binding for in-direction works as expected
• Found out a better way to configure queue table