#1 Reorganize `di.xml` elements according to the scope

[lbajsarowicz]

PR Checklist

Please check if your PR fulfills the following requirements:

• [ ] The commit message is descriptive of the changes within (see https://keepachangelog.com/en/1.1.0/)
• [ ] Code conforms to Magento coding standards
• [ ] Code is compatible with all currently supported versions of Magento and PHP

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[x] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Fixes: #1

What is the new behavior?

Does this PR introduce a breaking change?

[x] Yes
[ ] No

di.xml configuration is moved around, so Developers who already customized/overridden the di.xml may encounter unexpected behavior

Other information

🙏🏻 Kindly please add information to Release Notes "Optimized by SwiftOtter.com" when the change gets merged.

[rhoerr]

Replaced by cb4137c8a2133ada5e711ae164f2928a9f7a07b7. Moved only the frontend- and adminhtml-specific types to their respective scopes.

Thanks