Empty resolvedScopeCodes when config cache is cleaned

[andreas-wickberg-vaimo]

Also empty resolvedScopeCodes when config cache is cleaned.

Description

During setup:upgrade we change the name of the default store; magento will clean the config cache as part of saving the store view. However, ScopeCodeResolver's resolvedScopeCodes is not emptied, which means that it still maps 'stores',null to 'default', not the new name of the default store. This will break access to configurations.

Manual testing scenarios

With
/** @var \Magento\Store\Api\Data\WebsiteInterface */
protected $website;

/** @var \Magento\Store\Api\Data\GroupInterface */
protected $storeGroup;

/** @var \Magento\Store\Api\Data\StoreInterface */
protected $storeView;

we do
$this->website->getDefault();
$this->website->setCode($siteData['website']['code']);
$this->website->setName($siteData['website']['name']);
$this->website->setSortOrder($siteData['website']['sort_order']);
$this->website->setId(1);
$this->website->save();

    $this->storeGroup->load(1);
    $this->storeGroup->setName($siteData['store_group']['name']);
    $this->storeGroup->setId(1);
    $this->storeGroup->save();

    $this->storeView->load(1);
    $this->storeView->setCode($siteData['store_view']['code']);
    $this->storeView->setName($siteData['store_view']['name']);
    $this->storeView->setId(1);
    $this->storeView->save();
    $this->setLocale($siteData['store_view']['locale_code']);

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)

[magento-cicd2]

All committers have signed the CLA.

[okorshenko]

@andreas-wickberg-vaimo thank you for your contribution!