Target platform update behavior

As a user, when changing the target platform in application definition:

• Available packages list is reloaded (either the page is reloaded or only the appropriate zones - the latter is better of course)
• My package selection is kept after the reload is finished

Plan is:

• User has a TP with a package selection
  => e.g. JSF UI, DAM
• Package selection is stored in memory
• User changes target platform
  => Studio fetches the list of packages compatible with this TP
  => When packages are compatible, they are kept in the list
  => When packages are not available for this TP, they are removed
• At this point the list in memory is not changed
  => If user goes back to the original TP the package selection returns to what it was
• User saves
  => List is persisted both in files and in memory if needed
  => Packages for which definitions are known by Studio are put in a dedicated list that is used by Modeler
  => All packages are put anyway in a second list that will be used to generate the package.xml

Notes:

• At this stage, I cannot select a specific version for a package