Backport for Magento 2.2 - Fixes variables in configuration not being…

[hostep]

… replaced with actual values in the backend form fields.

(cherry picked from commit a8f1729)

Description (*)

This is a backport of #18067 for Magento 2.2

Fixed Issues (if relevant)

1. Since Magento 2.2.1, certain variables in the configuration get resolved to their actual value #15972: Since Magento 2.2.1, certain variables in the configuration get resolved to their actual value

Manual testing scenarios (*)

1. Setup a clean Magento from 2.2-develop branch
2. In the backend configuration go to: General > Web > Base URLs & Base URLs (Secure)
3. Enter {{unsecure_base_url}}media/ in "Base URL for User Media Files" and
   {{secure_base_url}}media/ in "Secure Base URL for User Media Files"
4. Save Config
5. Look at those two fields you just edited, they should remain unchanged

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)

[m2-assistant]

Hi @hostep. 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 2.2-develop instance - deploy vanilla Magento instance

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

[magento-engcom-team]

Hi @orlangur, thank you for the review.
ENGCOM-4662 has been created to process this Pull Request

[soleksii]

✔️ QA Passed

Result:

[m2-assistant]

Hi @hostep, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.