We moved almost all metadata outside of the install-image directory, and into a central user-specific location.  But Eclipse is still writing some of its cached data into the <install-image>/ccs/eclipse/configuration/ directory, if it is writeable.  If it is not writeable, it writes that data into HOME/.eclipse/ folder.

It should be possible to re-route the configuration data to our central location using the '-configuration' Eclipse flag.  This must be done consistently in all cases where ccs-server is launched - during normal IDE operation, but also during 'initialize' command (which is invoked at installation), and also when launching all headless apps (like 'createProject', 'importProject', 'buildProject').

It should only be done for desktop-mode.  In cloud-mode, we want to continue to have that data go into the <install-image>/ccs/eclipse/configuration/ directory.  That data gets generated during deployment, then it is accessed in a read-only way at runtime.  Having it in ccs/eclipse/configuration/ directory significantly improves IDE startup performance because that cached data is pre-generated at deployment-time and then shared by all users at runtime (the data includes the targetdb cache and discovered compiler/product caches, which are slow to generate).