[Forwardport] Postpone instantiation of session config by using a proxy

[hitesh-wagento]

Original Pull Request

#15929

Description

The session config is initialized too early, on initialisation of the HTTP response object. The init of this config object triggers the load of store-specific configuration, which then caches the resolved config path. This happens before the pathinfo is processed, which defines the current store in multi-storeview environment. By using a proxy the instantiation is postponed.

This problem was introduced in c18e36b.

Fixed Issues (if relevant)

1. Upgraded to Magento 2.2.4 from Magento 2.1.9 - Locale and Store Configuration issues 'Store View' Locale not being used on frontend, 'Default Config' Locale being used instead  #15205
2. 2.2.4: Wrong home page loaded in multi store setup  #15245

Manual testing scenarios

1. Magento 2.2.4
2. Multiple storeviews, e.g. for different languages (store en for en_US and de for de_DE)
3. Config web/url/use_store set to 1
4. Navigate to /de

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)

[hitesh-wagento]

@ishakhsuvarov Could you please check what cause failed travis?

Thanks,

[sidolov]

@hitesh-wagento , I'm closing this PR because original was closed due to performance degradation

[hostep]

@sidolov : the original PR was re-opened and merged, I'm re-opening this PR for re-evaluation if that's ok with you.

@hitesh-wagento : it's always better to wait with porting PR's, until the original has been approved :)

[hitesh-wagento]

@sidolov

Any update in this PR ?

Thanks

[ishakhsuvarov]

Hi @hitesh-wagento
You may observe Pull Request progress and status by looking at the "Projects" section in the right sidebar of the PR.

Currently this PR is finishing the process of manual testing.

[hitesh-wagento]

Hi @ishakhsuvarov

Thanks for reply.

[magento-engcom-team]

Hi @hitesh-wagento. Thank you for your contribution.
We will aim to release these changes as part of 2.3.0.
Please check the release notes for final confirmation.