Support Azure Repos active comment thread

[alikhajeh1]

Currently when Infracost posts a PR comment to Azure Repos, it marks the comment as closed to avoid triggering blocking behaviors or cause additional work for engineers. In our experience that works better for cost comments, and from Infracost Cloud you can configure certain checks (such as tagging policies) to block PRs until they’re resolved.

A user in the community reported the following, which sounds like having an env var/flag to change this behavior could be useful:

My aim is to enable a policy in AZDO to ensure that the cost changes have been acknowledged before merging the PR. To do this any new comment needs to appear as "active" as opposed to "closed". The current workaround is to install another 3rd party tool post and additional comment after infracost has posted. AFAIK the default state for a post is active.
We have a specific requirement that the team of engineers working on a particular project take accountability for the code that they deploy to the many envs. By posting "active" comments as opposed to "closed", the senior Dev merging the code into the main branch will have to acknowledge the cost changes that come with code change. We have this policy applied to main.

In our use case the same terraform code gets applied to each env with a seperate TFVARS. Each change made eventually gets deployed across multiple envs. Infracost highlights how each change affects DEV, INT, STA & PRD. I.e creating an new app service plan - ensuring that DEV is on a free or S1 tier where PRD could be on a S3. With the cost comment needing to be resolved, we can use this as a sign off.