Create automation to file and assign bugs for CI build breaks

To address recurring issues such as flakey tests, timeouts, etc. resulting in CIs breaking chronically, we should utilize azure dev ops automation features to auto-create and assign bugs for CI failures that meet certain criteria. Such criteria should seek to avoid noisy bugs related to PR changes failing CIs prior to being stable for merge.

No repository files, tests, or entry points are named. Start by reviewing the Azure DevOps automation capabilities and the existing CI failure workflow; done means qualifying CI failures automatically create and assign bugs while avoiding noisy failures from unstable pre-merge pull requests.

Written by the indexing model from the issue text.