InSAR update for 'insar stack overview' and 'external dem' issues

InSAR Stack Overview:

 - lists additional info in table

Support of ASTER, External and other DEMs in TOPO phase removal:

 - now 'partially' supports External DEM, limitations listed in jLinda repo,
   and in operators help;

 - reported issues with ASTER DEM are related to problems NEST-core and not jLinda.
Merge pull request #13 from pmar/insar_issues

InSAR update for 'insar stack overview' and 'external dem' issues
Fix for getGeoPos() of AsterElevationModel

AsterElevationModel.getGeoPos() now correctly computes Geographic
coordinates as a function of pixel index for ASTER DEM. This bug was
effecting correct use of ASTER DEM in InSAR modules, and modules
using Delaunay interpolation.

All InSAR tests passing.
Merge pull request #14 from pmar/insar_issues

Fix for correct handling of ASTER in InSAR modules and for Delaunay interpolation
fixes to 5.0.9 for release
fix deflt orbit constant
fix tsx detected
fix for beam-gpf version in nest-gpf maven archetypes
upgrade java version in compuler plugin
Merge pull request #15 from pmar/build

fix archetypes for clean build
fixes for TSX reading, landmask, ENVISAT dd, RTC nodata
5.0.12 TSX detected bands fix
Stop tracking jLinda - jLinda now an artifact/dependency

- jLinda is now used in NEST as separate dependency/artifact

- jLinda artifacts are distributed via maven.ppolabs.me

    Dependency for the core functionality:

        <dependency>
           <groupId>org.jlinda</groupId>
           <artifactId>jlinda-core</artifactId>
           <version>0.5</version>
        </dependency>

    Dependency for NEST operators:

        <dependency>
           <groupId>org.jlinda</groupId>
           <artifactId>jlinda-nest</artifactId>
           <version>0.5</version>
        </dependency>

- jLinda and NEST can still be jointly compiled

    1) jLinda source tree should be sourced into NEST. Preferably,
    using git-submodules, or simply by copying jLinda tree into NEST.

      For example invoking:

        $ git submodule add git@github.com:ppolabs/jlinda.git

      in top of NEST tree, will create jLinda module within NEST, that can
      be tracked and maintained as independent project.

    2) For compiling there are two (identical) profiles added to the central
    pom.xml of NEST: 'jlinda' and 'insar'

      Command to compile NEST and jLinda together:

        $ mvn compile -P insar
oops removed accidentally tracked submodule
jlinda version -> 0.6-SNAPSHOT
still removing submodule leftovers
Merge pull request #16 from pmar/unstable

Unstable
actually submodules should be tracked
Start tracking jLinda as submodule