Update connection string after database restore to new location (4384087)

The most obvious/first symptom is JobServers attempting to connect to the "old" database location and not process jobs.

If the admin tries to run sync projects, these will also fail with DB connection errors.

If you are attempting to create a dev instance by cloning a production instance, the errors can be worse as the test-job servers or projects may end up connecting to the production DB and making changes to live target systems

The database connection string is stored in multiple places in the Identity Manager database, and on the JobServers in the local configuration files

• In Designer > Base Data > General > Databases 
  This is the "main" connection string used when creating "new" job servers, projects, etc.
• For each Job Server, the settings defining the JobServer/Queue in Designer must be updated. 
  The local copy of the config file must be updated
• In Synchronization Editor, each synchronization project has a copy of the database connection string

Note - storing multiple copies of the connection string is by design to facilitate distributed environments. However this flexibility caused more work when moving or cloning databases.

Update ALL references to the connection string both in Designer, Synchronization Editor and in the local JobServer configuration files.