…(HypeMC)This PR was merged into the 6.2 branch.Discussion----------[DependencyInjection] Add missing use statement in test| Q             | A| ------------- | ---| Branch?       | 6.2| Bug fix?      | yes| New feature?  | no| Deprecations? | no| Tickets       | -| License       | MIT| Doc PR        | -Looks like#46279 removed a use statement by accident. This PR returns the missing use statement & fixes the tests.Commits-------b03cbe6 [DependencyInjection] Add missing use statement in test

…for excluded services (apfelbox)This PR was merged into the 6.2 branch.Discussion----------[FrameworkBundle] container:debug CLI output improvements for excluded services| Q             | A| ------------- | ---| Branch?       | 6.3| Bug fix?      | no| New feature?  | yes (not sure)| Deprecations? | no| Tickets       | —| License       | MIT| Doc PR        | —<!--Replace this notice by a short README for your feature/bugfix.This will help reviewers and should be a good start for the documentation.Additionally (seehttps://symfony.com/releases): - Always add tests and ensure they pass. - Bug fixes must be submitted against the lowest maintained branch where they apply   (lowest branches are regularly merged to upper ones so they get the fixes too). - Features and deprecations must be submitted against the latest branch. - For new features, provide some code snippets to help understand usage. - Changelog entry should followhttps://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry - Never break backward compatibility (seehttps://symfony.com/bc).-->Normally I test whether the exclusion rules from the service container of my bundles work correctly by just using the `debug:container` command and looking whether my excluded services occur in the last.However, due to the latest changes in#46279 all services (excluded or not) are always in this list.You need to open the definition to see if it was excluded:![CleanShot 2022-12-12 at 11 01 08](https://user-images.githubusercontent.com/1032411/207017120-50d3c263-ce7a-4c92-bb7e-8a8f86c47983.png)This PR proposes two things:1. add a more prominent warning to the service definition details screen that the service is excluded![CleanShot 2022-12-12 at 11 01 52](https://user-images.githubusercontent.com/1032411/207017261-44495233-f513-4c29-bb6d-469eb0418080.png)(wording tbd)2. mark the services as excluded in the list (right now by graying them out):![CleanShot 2022-12-12 at 11 02 44](https://user-images.githubusercontent.com/1032411/207017481-993010da-3364-49dd-b7e0-4f3c07f14ad5.png)If this looks like something you want to include, I will add the "graying out" part to the table view as well.wdyt?Commits-------9d2f10f Hide excluded services from container debug list

…s92)This PR was merged into the 6.2 branch.Discussion----------Hide definitions bearing the `container.excluded` tag| Q             | A| ------------- | ---| Branch?       | 6.2| Bug fix?      | yes| New feature?  | no| | Depreciation? | no| Tickets       |Fix#50417| License       | MIT| Doc PR        | -Normally I test whether the exclusion rules from the service container of my bundles work correctly by just using the `debug:container` command and looking whether my excluded services occur in the last.However, due to the latest changes in#46279 all folders and subfulders (excluded or not) are always in this list.You need to open the definition to see if it was excluded:<img width="1463" alt="Service Container" src="https://github.com/symfony/symfony/assets/31630905/609d75b7-3840-4c7d-b3ec-4c0d4bc158e6">For example, `Command`, `Query`, `Entity` are folders, but they are specified as services in the container.This PR fixes this problem to ignore definitions bearing the container.excluded tag if those are to be hidden for Descriptors: `JsonDescriptor`,  `MarkdownDescriptor`, `TextDescriptor` and `XmlDescriptor`.After fixes problem:<img width="1351" alt="Снимок экрана 2023-05-27 в 17 03 19" src="https://github.com/symfony/symfony/assets/31630905/e2aecdeb-9261-4d98-af10-a74db7f1e46a">Commits-------2c668ba Ignore definitions bearing the `container.excluded` tag