[policy, no patch] When should service arguments be wrapped?

Problem/Motivation

Currently, all core service definitions put their arguments on one long line:

arguments: ['@something', '@something.else', '@another_one', '@getting_long', '@cheaper', '@by.the.dozen']

In reviewing #3041885: Display relevant Security Advisories data for Drupal, @larowlan pointed out that sometimes, with services that have many dependencies, these lines are harder to read, and might be better if we used the list format:

arguments:
  - '@something'
  - '@something.else'
  - '@another_one'
  - '@getting_long'
  - '@cheaper'
  - '@by.the.dozen'

At his suggestion, I'm opening this issue to decide when, if ever, service arguments should span multiple lines, instead of one long line.

Benefits

Increased readability and reduces the need for side scrolling.

Three supporters required

1. https://www.drupal.org/u/borisson_ (2025-08-22)
2. https://www.drupal.org/u/{userid} (yyyy-mm-dd they added support)
3. https://www.drupal.org/u/{userid} (yyyy-mm-dd they added support)

Proposed changes

Current text

Proposed text

Notes

Remaining tasks

1. Create this issue in the Coding Standards queue, using the defined template
2. Add supporters
3. Create a Change Record
4. Review by the Coding Standards Committee
5. Coding Standards Committee takes action as required
6. Discussed by the Core Committer Committee, if it impacts Drupal Core
7. Final review by Coding Standards Committee
8. Documentation updates
   1. Edit all pages
   2. Publish change record
   3. Remove 'Needs documentation edits' tag
9. If applicable, create follow-up issues for PHPCS rules/sniffs changes

For a full explanation of these steps see the Coding Standards project page
upstream work on a sniff, https://github.com/slevomat/coding-standard/issues/1684