test: update formatting of multi-line annotations

It's hard to grok the change from the snapshot diffs alone, so here's
one example. Before:

    PYI021.pyi:15:5: PYI021 [*] Docstrings should not be included in stubs
       |
    14 |   class Baz:
    15 |       """Multiline docstring
       |  _____^
    16 | |
    17 | |     Lorem ipsum dolor sit amet
    18 | |     """
       | |_______^ PYI021
    19 |
    20 |       def __init__(self) -> None: ...
       |
       = help: Remove docstring

And now after:

    PYI021.pyi:15:5: PYI021 [*] Docstrings should not be included in stubs
       |
    14 |   class Baz:
    15 | /     """Multiline docstring
    16 | |
    17 | |     Lorem ipsum dolor sit amet
    18 | |     """
       | |_______^ PYI021
    19 |
    20 |       def __init__(self) -> None: ...
       |
       = help: Remove docstring

I personally think both of these are fine. If we felt strongly, I could
investigate reverting to the old style, but the new style seems okay to
me.

In other words, these updates I believe are just cosmetic and not a bug
fix.

Author: BurntSushi

crates/ruff_linter/src/rules/flake8_async/snapshots/ruff_linter__rules__flake8_async__tests__ASYNC100_ASYNC100.py.snap

@@ -1,102 +1,90 @@
 ---
 source: crates/ruff_linter/src/rules/flake8_async/mod.rs
-snapshot_kind: text
 ---
 ASYNC100.py:8:5: ASYNC100 A `with trio.fail_after(...):` context does not contain any `await` statements. This makes it pointless, as the timeout can only be triggered by a checkpoint.
   |
 7 |   async def func():
-8 |       with trio.fail_after():
-  |  _____^
+8 | /     with trio.fail_after():
 9 | |         ...
   | |___________^ ASYNC100
   |
 
 ASYNC100.py:18:5: ASYNC100 A `with trio.move_on_after(...):` context does not contain any `await` statements. This makes it pointless, as the timeout can only be triggered by a checkpoint.
    |
 17 |   async def func():
-18 |       with trio.move_on_after():
-   |  _____^
+18 | /     with trio.move_on_after():
 19 | |         ...
    | |___________^ ASYNC100
    |
 
 ASYNC100.py:45:5: ASYNC100 A `with anyio.move_on_after(...):` context does not contain any `await` statements. This makes it pointless, as the timeout can only be triggered by a checkpoint.
    |
 44 |   async def func():
-45 |       with anyio.move_on_after(delay=0.2):
-   |  _____^
+45 | /     with anyio.move_on_after(delay=0.2):
 46 | |         ...
    | |___________^ ASYNC100
    |
 
 ASYNC100.py:50:5: ASYNC100 A `with anyio.fail_after(...):` context does not contain any `await` statements. This makes it pointless, as the timeout can only be triggered by a checkpoint.
    |
 49 |   async def func():
-50 |       with anyio.fail_after():
-   |  _____^
+50 | /     with anyio.fail_after():
 51 | |         ...
    | |___________^ ASYNC100
    |
 
 ASYNC100.py:55:5: ASYNC100 A `with anyio.CancelScope(...):` context does not contain any `await` statements. This makes it pointless, as the timeout can only be triggered by a checkpoint.
    |
 54 |   async def func():
-55 |       with anyio.CancelScope():
-   |  _____^
+55 | /     with anyio.CancelScope():
 56 | |         ...
    | |___________^ ASYNC100
    |
 
 ASYNC100.py:60:5: ASYNC100 A `with anyio.CancelScope(...):` context does not contain any `await` statements. This makes it pointless, as the timeout can only be triggered by a checkpoint.
    |
 59 |   async def func():
-60 |       with anyio.CancelScope(), nullcontext():
-   |  _____^
+60 | /     with anyio.CancelScope(), nullcontext():
 61 | |         ...
    | |___________^ ASYNC100
    |
 
 ASYNC100.py:65:5: ASYNC100 A `with anyio.CancelScope(...):` context does not contain any `await` statements. This makes it pointless, as the timeout can only be triggered by a checkpoint.
    |
 64 |   async def func():
-65 |       with nullcontext(), anyio.CancelScope():
-   |  _____^
+65 | /     with nullcontext(), anyio.CancelScope():
 66 | |         ...
    | |___________^ ASYNC100
    |
 
 ASYNC100.py:70:5: ASYNC100 A `with asyncio.timeout(...):` context does not contain any `await` statements. This makes it pointless, as the timeout can only be triggered by a checkpoint.
    |
 69 |   async def func():
-70 |       async with asyncio.timeout(delay=0.2):
-   |  _____^
+70 | /     async with asyncio.timeout(delay=0.2):
 71 | |         ...
    | |___________^ ASYNC100
    |
 
 ASYNC100.py:75:5: ASYNC100 A `with asyncio.timeout_at(...):` context does not contain any `await` statements. This makes it pointless, as the timeout can only be triggered by a checkpoint.
    |
 74 |   async def func():
-75 |       async with asyncio.timeout_at(when=0.2):
-   |  _____^
+75 | /     async with asyncio.timeout_at(when=0.2):
 76 | |         ...
    | |___________^ ASYNC100
    |
 
 ASYNC100.py:85:5: ASYNC100 A `with asyncio.timeout(...):` context does not contain any `await` statements. This makes it pointless, as the timeout can only be triggered by a checkpoint.
    |
 84 |   async def func():
-85 |       async with asyncio.timeout(delay=0.2), asyncio.TaskGroup(), asyncio.timeout(delay=0.2):
-   |  _____^
+85 | /     async with asyncio.timeout(delay=0.2), asyncio.TaskGroup(), asyncio.timeout(delay=0.2):
 86 | |         ...
    | |___________^ ASYNC100
    |
 
 ASYNC100.py:95:5: ASYNC100 A `with asyncio.timeout(...):` context does not contain any `await` statements. This makes it pointless, as the timeout can only be triggered by a checkpoint.
    |
 94 |   async def func():
-95 |       async with asyncio.timeout(delay=0.2), asyncio.timeout(delay=0.2):
-   |  _____^
+95 | /     async with asyncio.timeout(delay=0.2), asyncio.timeout(delay=0.2):
 96 | |         ...
    | |___________^ ASYNC100
    |

crates/ruff_linter/src/rules/flake8_async/snapshots/ruff_linter__rules__flake8_async__tests__ASYNC110_ASYNC110.py.snap

@@ -1,48 +1,42 @@
 ---
 source: crates/ruff_linter/src/rules/flake8_async/mod.rs
-snapshot_kind: text
 ---
 ASYNC110.py:7:5: ASYNC110 Use `trio.Event` instead of awaiting `trio.sleep` in a `while` loop
   |
 6 |   async def func():
-7 |       while True:
-  |  _____^
+7 | /     while True:
 8 | |         await trio.sleep(10)
   | |____________________________^ ASYNC110
   |
 
 ASYNC110.py:12:5: ASYNC110 Use `trio.Event` instead of awaiting `trio.sleep` in a `while` loop
    |
 11 |   async def func():
-12 |       while True:
-   |  _____^
+12 | /     while True:
 13 | |         await trio.sleep_until(10)
    | |__________________________________^ ASYNC110
    |
 
 ASYNC110.py:22:5: ASYNC110 Use `asyncio.Event` instead of awaiting `asyncio.sleep` in a `while` loop
    |
 21 |   async def func():
-22 |       while True:
-   |  _____^
+22 | /     while True:
 23 | |         await anyio.sleep(10)
    | |_____________________________^ ASYNC110
    |
 
 ASYNC110.py:27:5: ASYNC110 Use `asyncio.Event` instead of awaiting `asyncio.sleep` in a `while` loop
    |
 26 |   async def func():
-27 |       while True:
-   |  _____^
+27 | /     while True:
 28 | |         await anyio.sleep_until(10)
    | |___________________________________^ ASYNC110
    |
 
 ASYNC110.py:37:5: ASYNC110 Use `anyio.Event` instead of awaiting `anyio.sleep` in a `while` loop
    |
 36 |   async def func():
-37 |       while True:
-   |  _____^
+37 | /     while True:
 38 | |         await asyncio.sleep(10)
    | |_______________________________^ ASYNC110
    |