Update class deprecations to implement "Concrete, instantiated classes" policy

I moved the deprecation error triger in classes:
3 core/lib/Drupal/Core/Asset/JsCollectionOptimizer.php
2 core/lib/Drupal/Core/Asset/CssCollectionOptimizer.php

and deleted the redundant trigger from
4 core/lib/Drupal/Core/Http/RequestStack.php

I am not really sure how to proceed with
5 core/modules/system/tests/modules/deprecation_test/src/Deprecation/DrupalStandardsListenerDeprecatedClass.php
6 core/modules/system/tests/modules/deprecation_test/src/Deprecation/FixtureDeprecatedClass.php
because they are "arbitrarily deprecated in order to test the deprecation error handling properties of DrupalStandardsListener."

and
1 core/lib/Drupal/Component/Plugin/PluginHelper.php
does not accept a contruct.

I tried to look for other classes deprecated but could not find any concrete, instantiated classes.

please help and review

I think this is good but not sure the policy for moving existing deprecation triggers.

@lucienchalom, thanks for working on this! This is a good start. For PluginHelper and RequestStack add a constructor (stated in policy) and then the test will need to be changed to instantiate the class. And the same for the test modules because we should be using the standard set in policy and well as testing that.

@smustgrave, There is no policy for moving deprecations. There is a policy for concrete classes and core needs to change to met the current standard.

The issue summary has a sample grep to find the instances that need to be changed. Has anyone worked to improve on that or verify that it is accurate?

Rebased and updated the issue summary.

I think that this is suitable as a novice level issue.