Remove development.services.yml from Drupal's composer scaffolding

Changed the file name from development.services.yml to example.development.services.yml

Hi Deepthi
Good job, I have tested it and its working fine.

Changed "['sites/development.services.yml', 'assets/scaffold/files/development.services.yml']" in /core/tests/Drupal/Tests/ComposerIntegrationTest.php on line 124

changes done in composer.json

Thanks, current patch looks clean to me, and I think it is a valid proposal (and a good idea).

I had a look at how we're currently using development.services.yml file, should we change these lines on sites/example.settings.local.php, since the file may or may not be there?

/**
 * Enable local development services.
 */
$settings['container_yamls'][] = DRUPAL_ROOT . '/sites/development.services.yml';

And also at least update the documentation on the example.development.services.yml file itself:

# To activate this feature, follow the instructions at the top of the
# 'example.settings.local.php' file, which sits next to this file.

Yes, this is not really an example as it's actually included now by most settings.local.php files and would break those sites as they updates. easy enough to fix, but then again, nothing stops anyone from copying it already now.

Might be enough to just comment in the file and on the include line that it should be copied to customize it?

As proposed this'd be a BC break. #11 sounds like a better approach indeed.

FWIW I found a related problem in #3272587 - changes made in development.services.yml won't override what's in services.yml, so there might be another problem here.

Re-rolled patch#17 for 9.5.x . Thanks @Neslee Canil Pinto

Added patch #23 in Drupal 10.1.x

@Shubham Sharma: Rerolls are not automatically needed if a Drupal dev branch version changes. In many cases, the patch still applies. If you click the "Add test / retest" link on the most recent patch of a given issue, you can test the patch on 10.1.x (or whatever the current dev branch is). If the patch applies there, then no reroll is needed.

You added a reroll that was not needed - I noticed you doing the same in at least 7 other recent issues. Credit is not granted for unnecessary rerolls.

Won't this be made mute by #3278887: Update development.services.yml to include twig debug by default ?

Should this be closed for that one? Credit to be moved over of course.

Tagging for framework manager thought (May not be the correct tag but there's no sub system maintainer for base system in the MAINTAINERS.txt file)

whoops, I've commented on wrong issue, see link in previous comment. My apologies.

Think a framework manager would have to answer that but I would be for it. Almost all projects we have to tell composer to not touch that file.