Split the TestShell Refactoring cache file into 2 files to support better sharing options

The current TestShell Refactoring cache file is a composite of local content and DB content
It's located under C:\Users\user\AppData\Local\QualiSystems and is called refactoringCache.dat

This works well in theory, but there are downsides to it.
After an upgrade or patch, all users will need to update their refactoring file which puts additional stress on the system. The larger the userbase, the higher the impact on the server and DB.
Additionally, if terminal servers are used to host the clients i.e. Windows 2012, then the server has higher impact due to multiple users all refactoring at once.

My proposal is to separate the refactoring file into 2 parts: 1. for local and 1 for the DB

At login (via a scheduled task) or manual script execution post an upgrade/patch or other impacting event and before users login to TestShell Studio, an already updated DB refactoring data file could be copied into the user's local windows folder to overwrite the DB refactoring file, thus greatly reducing overheads and the time required to refactor after the change to the system.

This could also be an option after a long time of no use or at 1st time using TestShell on a different machine i.e. where users can migrate between various Client VMs based on system load.

This capability to re-use an updated refactoring cache file has been proven to great effect in our environment (better to use a user with no local content to perform the 1st refactoring after the update).