Update eclipse dependencies to version 3.8

Since there is no public maven repository with
newer eclipse dependencies, use the company
internal repository.
Update eclipse plugin usage with new technique

There is a better technique for eclipse integration
which uses a target platform instead of linked
resources.
Document why "lazy" is used
Disable embedding of dependencies

Embedding was used even for JARs which were
already bundles. A better solution is to import JARs
which are bundles and treat non-bundles as a special
case. Most popular Java projects (ie. guava, apache
commons) produce valid OSGi bundles.
Disable "uses" in manifest generation
Add maven version prerequisites
Remove unused maven properties
Add IntelliJ IDEA plugin configuration
Manage project dependency versions in parent POM
Use snapshot versioning
Synchronize artifact IDs
Synchronize package name to match artifact ID
Update description
Remove unused configuration
Configure eclipse-plugin to use new technique

The new technique uses eclipse "target platforms"
instead of embedding dependencies.
Fix package names
Update gitignore
Change from view to standalone application
Exclude circular dependencies

These dependencies were converted from p2/eclipse to Maven using mt4e.

The tool generated dependencies which contain circular dependencies on
themselves.

This does not appear to affect eclipse but breaks the IntelliJ IDE.
Add dependencies to View

The view depends on some classes in another bundle "eclipse-plugin-utils"