MAGETWO-80581: Merge code from 2.2.0 release branches into "2.2-develop" branches

[paliarush]

Scope

Task

• MAGETWO-80581 Merge code from 2.2.0 release branches into "2.2-develop" branches

Bamboo CI Builds

• M2, CI (CE + EE) - 2.2-develop - L1
• M2, CI (CE + EE) - 2.2-develop - L2
• M2, CI (CE + EE) - 2.2-develop - L3
• M2, CI (CE + EE) - 2.2-develop - L4
• M2, CI (CE + EE) - 2.2-develop - Performance Acceptance Tests
• M2, CI (CE + EE) - 2.2-develop - Sample Data Tests
• Semantic Version Checker - 2.2-develop

Related Pull Requests

https://github.com/magento/magento2ce/pull/1538
https://github.com/magento/magento2ee/pull/729
https://github.com/magento/magento2b2b/pull/286
https://github.com/magento/magento2-sample-data-ee/pull/22

Checklist

• PR is green on M2 Quality Portal
• Jira issues have accurate summary, meaningful description and have links to relevant documentation at the story/task level
• Semantic Version build failure is approved by architect (not applicable)
• Pull Request approved by architect @kandy
• Pull Request quality review performed by @vgoncharenko
• All unstable functional acceptance tests are isolated (if any)
• All linked Zephyr tests are approved by PO and have Ready to Use status
• Travis CI build is green (for mainline CE only)
• Jenkins Extended FAT build is green

[magento-cicd2]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ paliarush
❌ magento-team

[kandy]

Approved by Architect

[dvoskoboinikov]

Approved by GK.