[3924] Fix merging implicit multiline strings that have inline comments

[henriholopainen]

Description

After some discussions in the issue, we decided not to merge implicit multiline strings if there are inline comments on the string lines. Added description of behaviour to Preview style documentation.

Checklist - did you ...

• Add an entry in CHANGES.md if necessary?
• Add / update tests if necessary?
• Add new / update outdated documentation?

[github-actions]

diff-shades results comparing this PR (74d46c8) to main (9edba85). The full diff is available in the logs under the "Generate HTML diff report" step.

╭─────────────────────── Summary ────────────────────────╮
│ 1 projects & 1 files changed / 4 changes [+2/-2]       │
│                                                        │
│ ... out of 2 498 892 lines, 11 747 files & 23 projects │
╰────────────────────────────────────────────────────────╯

Differences found.

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

[henriholopainen]

The documentation build error looks like it's not rooted in these changes:

Configuration error:
There is a programmable error in your configuration file:

-------

pkg_resources.DistributionNotFound: The 'black' distribution was not found and is required by the application

Will look into the diff-shades

[henriholopainen]

Hmm, can't reproduce the diff-shades locally:

% black --version
black, 0.1.dev1687+g9edba85.d20231019 (compiled: no)
Python (CPython) 3.11.3
% black --diff ../django/tests/admin_scripts/tests.py
All done! ✨ 🍰 ✨
1 file would be left unchanged.

% black --version
black, 0.1.dev1694+g74d46c8.d20231019 (compiled: no)
Python (CPython) 3.11.3
% black --diff ../django/tests/admin_scripts/tests.py
All done! ✨ 🍰 ✨
1 file would be left unchanged.

Is there some special configuration in the diff Action?

edit: oh, it's the --preview diff. That should be fine, right?