Add Azure Devops as a -format option.

[StefanBRas]

Adds option to print messages in an error format for azure pipelines, following https://learn.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands?view=azure-devops&tabs=bash#usage.

In the command line it looks like:

> cargo run -p ruff_cli -- check ../python_testing/example_tag.py --no-cache --format azure-devops
##vso[task.logissue type=error;sourcepath=/home/stefan/dev/python_testing/example_tag.py;linenumber=2;columnnumber=8;code=F401;]/home/stefan/dev/python_testing/example_tag.py:2:8: F401 `math` imported but unused
##vso[task.logissue type=error;sourcepath=/home/stefan/dev/python_testing/example_tag.py;linenumber=3;columnnumber=8;code=F401;]/home/stefan/dev/python_testing/example_tag.py:3:8: F401 `sys` imported but unused

In the pipeline logs it shows as:

And in the pipeline summary it shows as:

Which isn't particularly pretty but apparently how Azure Devops think it should be displayed.

[charliermarsh]

Thanks!

I'm not sure if it makes sense have the error information in both the message and in the logging metadata, as it's then displayed twice but I just followed the same structure as the Github formatting. I can remove it from the message if you want :)

If the messages appear in the logs without repeating, then they can be omitted. I think we repeat them with GitHub because if you only output the annotations, the messages appear in the PR view but not in the raw logs.

[charliermarsh]

Would it be reasonable to shorthand this to azure, rather than azure-devops?

[StefanBRas]

Great, I'll remove the duplicate info then :)

I'm not sure about the renaming, since just "azure" refers to lots of different services where DevOps is one of them. But I can't come up with any other service that needs to emit logs from ruff, so it's probably fine.

I have no strong opinions either way, so I'll just rename it :)