Region doesn't updates after changing country and leaving region select unselected

[Stepa4man]

Preconditions

1. Create user
2. Create user address with country "United States" and region "Alabama"

Steps to reproduce

1. Go to created customer page
2. Go to address customer address tab
3. Hit edit action for the created address at the addresses grid
4. Change the country to France
5. Don't choose any region
6. Save address
7. Run in browser console jQuery('[data-index="region_id_input"]').show() to display hidden State/Province field (second field with the same label)

Expected result (*)

1. Second State/Province input is empty

Actual result (*)

1. Second State/Province input has value Alabama (which is saved to db after hitting Save button)

Additional

The same issue is applicable for source edit page because the main point here is Region UI component which doesn't empty hidden region input with Region label for the described case.

###Env
Mac OS
Valet+ (PHP7.1, NGINX, MYSQL)
Magento 2.3-develop branch

[m2-assistant]

Hi @Stepa4man. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

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

@Stepa4man do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @Stepa4man. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[Stepa4man]

@magento give me 2.2-develop instance

[magento-engcom-team]

Hi @Stepa4man. Thank you for your request. I'm working on Magento 2.2-develop instance for you

[magento-engcom-team]

Hi @Stepa4man, here is your Magento instance.
Admin access: https://i-23460-2-2-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[Stepa4man]

@magento give me 2.1-develop instance

[magento-engcom-team]

Hi @Stepa4man. Thank you for your request.
Unfortunately, I can only deploy instances for 2.2 and 2.3 release lines