Add framework for settings backwards compatibility #477
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Fixes #464.
Stores the plugin's version in the user's settings to allow version detection in the future. Furthermore, though
Settingsremains the usual object with atemplateList(and perhaps other fields in the future (cf. #469?)), the classPersistentSettingsnow acts as if settings are saved as anElement(i.e. as XML). When settings are loaded,PersistentSettingshas the opportunity to modify the XML before deserialising it into aSettings. Therefore, if there are incompatibilities between versions that the default XML deserialiser cannot handle, a small bit of code can be added to make these modifications automatically.