[cobaltt7]

Description

Closes #4882
Instead of requiring no parens when there's no delimiters (as discussed on the issue), I choice to respect users' choice. While this adds a dependency on previous formatting, many of the examples in the test case were formatted worse without the parens.

Checklist - did you ...

• [y] Implement any code style changes under the --preview style, following the stability policy?
• [y] Add an entry in CHANGES.md if necessary?
• [y] Add / update tests if necessary?
• [-] Add new / update outdated documentation?

[github-actions]

diff-shades results comparing this PR (b7c13cc) to main (9a1f64e):

--preview style (View full diff):

╭───────────────────────── Summary ──────────────────────────╮
│ 11 projects & 84 files changed / 2006 changes [+584/-1422] │
│                                                            │
│ ... out of 3 146 638 lines, 14 240 files & 22 projects     │
╰────────────────────────────────────────────────────────────╯
Differences found.

--stable style: no changes

---

What is this? | Workflow run | diff-shades documentation

[cobaltt7]

Note: it was mentioned on the issue how triple-quoted strings were always wrapped in parens too. I changed that to only wrap concatenated strings in parens (as with single-quoted strings), but kept those dicts containing single triple quoted strings broken.

# Stable
{"a": """
"""}

# Preview (main)
{
     "a": (
        """
"""
    )
}

# Preview (this PR)
{
     "a": """
"""
}