Exclude SessionProgress from DI

[cedric-anne]

Checklist before requesting a review

• I have read the CONTRIBUTING document.
• I have performed a self-review of my code.

Description

See #18296 (comment)

Not sure it is necessary. There is no reference to this class in any service, so the DI will probably never try to instanciate it.

[AdrienClairembault]

I see, I forgot that the container doesn't instantiate service that are not used so this is why it doesn't trigger an error here.
Not sure if this is needed then.

[AdrienClairembault]

By the way are we looking into having a dedicated Service directory at some point to avoid having to manually register new services (or maybe we should use the exisiting DependencyInjection directory ?).

[Pierstoval]

By the way are we looking into having a dedicated Service directory at some point to avoid having to manually register new services (or maybe we should use the exisiting DependencyInjection directory ?).

Nope, "service" is too vague, anything can be a service, and that's exactly the reason why by default it's better to include almost everything, and to exclude non-service objects one-by-one. And if you have two, three or more of them, a subdirectory (like "DTO", "Entity", "Data", etc.) is necessary for these classes.

If you have a "Service" namespace/directory, you'll end up just like the roots of src/: hundreds of unsorted, unorganized and unarchitectured classes.