Changing the tag ID does not fully change the config

Problem/Motivation

If you change the tag ID in an existing site, the config of the site does not fully change to match, causing deployment problems.

Steps to reproduce

1. Set up Google Tag with an ID. Export configuration. The name of the google_tag.container.*.yml file will match the tag ID.
2. Change the tag ID in the UI. Export configuration again. The existing google_tag.container.*.yml file will now contain the new ID although its name is still the old ID.
3. In the database, run `select * from config where name like 'google%';` The old ID will still be present, and the new one absent.
4. If convenient, copy the database to a new environment. Config will show out of sync. Import the config. Config will now appear to be in sync, but there will no longer be a Google tag ID in the UI.

Proposed resolution

unknown