[Backport] Fix issue with unexpected changing of subscription status after customer saving

[arendarenko]

Original Pull Request

#18488

Description

If in some cases (for example: after migration data from M1) customer will have store_id = 0 and there are subscriber that related to this customer, after re-saving customer data, it might cause unexpected "unsubscribe" letter which would confuse customer experience.

My changes solves this problem because of adding additional checking storeId and if it's 0, getting it directly from the website.

Manual testing scenarios

1. Create new customer
2. Create customer
3. Go to MySQL and set store_id = 0 in customer_entity table for this customer
4. Go to MySQL and create record in newsletter_subscriber for this customer but with correct store_id and subscribe_status = 1.
5. Go to backend -> Customers and open it for edit
6. Change some customer data (for example, name) and save user

Expected result:
Nothing, except saving customer data, will happen

Actual result:
Customer will receive unsubscription letter.

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-engcom-team]

Hi @alexeya-ven. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento-engcom-team give me test instance - deploy test instance based on PR changes
• @magento-engcom-team give me $VERSION instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

[magento-engcom-team]

Hi @ihor-sviziev, thank you for the review.
ENGCOM-3276 has been created to process this Pull Request

[sidolov]

Hi @alexeya-ven , unfortunately, we cannot reproduce described issue, maybe you can provide additional steps?
Thank you!

[ihor-sviziev]

Maybe it was fixed by #18643, but I don't think so

[magento-engcom-team]

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

Please, consider to port this solution to 2.3 release line.
You may use Porting tool to port commits automatically.