build: Remove redundant repository references

The parent poms already list all Maven repositories needed.
build: Sync lists of feature repositories

We refer to service mix feature repositories in three
different places:

- Our own feature repositories
- The features-maven-plugin
- The Karaf feature configuration file

Unfortunately this repetition cannot be completely avoided (even
though it breaks DRY).

This patch syncs the lists of feature repositories, ensuring that
the features we resolve at runtime are the same as the features
resolved by the maven plugin. Specifically this ensures that all
the bundles needed at runtime have been installed in the Karaf
system repository during build time.

As a consequence no extra bundles will be downloaded the first time
Mantychore is started. Thus Mantychore can now be started without
a network connection. Even more important, Mantychore integration
tests can be executed without a network connection. The integration
tests also finish significantly faster as all dependencies are
present in the test environment.

Note that I changed the configuration of the features-maven-plugin
to install dependencies too. By itself this change is however not
enough because the various feature repositories shipped with
ServiceMix have overlapping feature descriptors with inconsistent
dependencies. Thus before this patch the cxf repository resolved
at build time was different than the one resolved at runtime.
build: Remove activemq dependencies

Several bundles import activemq packages even though they
don't make use of it. These dependencies needlessly force
activemq to be loaded.
build: Refactor feature repositories

The OSGi feature repositories of OpenNaaS and Mantychore had
several problems:

- They were not self-contained in the sense that installing
  the feature required one to manually ensure that
  requirements had been installed before.

- They were split into a deps feature and a core feature. The
  deps feature was really a usable feature in itself; it simply
  embodied dependencies. The core feature on the other hand
  contained all features of the product. This didn't allow
  for selectively installing features of the product.

- Dependencies were not flagged as dependencies.

- Bundle version numbers were hardcoded.

- Some of the depenendencies are unnecessary (like activemq),
  and others are only used by periferal functionality (like
  cxf). Forcing these dependencies are pre-requisites means
  that integration testing becomes unnecessarily slow as
  all dependencies have to be started for every test.

This patch refactors the feature repositories.

- There are no longer any -deps features. Features are now
  self-contained with all dependencies specified. This means
  one can do 'feature:install x' and expect it to install all
  prerequisites.

- Features are split according to what one can consider
  "end-user features", eg router, network and bod are features,
  and so is junos. The core opennaas functionality is a feature
  too.

- All version numbers are parameterized.

- I tried to identify the essential dependencies of each feature.

Testing done: Unit and integration tests pass. I manually
installed each feature on a fresh build to verify that they
can resolve all bundle dependencies. I ran Mantychore and
configured it to connect to an Olive. I verified that basic
commands like creating logical routers and subintefaces work.
build: Rename features to opennaas naming scheme

The patch adjusts the feature names to avoid the name 'mantychore'. All
feature names are prefixed opennaas- (with a couple of exceptions for
test bundles).

I am not using the proposed opennaas-extensions- prefix for feature
names as it would make the names unusually long compared to other
ServiceMix feature names. Prefixing with opennaas- should be enough to
make the names fairly unique.

I renamed mantychore-base to mantychore-cim as the feature is about
representing the CIM model. In its current form the feature also holds
the network model, but this is because the dependency between the two is
upside down. Once the dependency has been inverted the network model
bundle should be moved to the network feature. Similarly the
queuemanager bundle should be part of opennaas-core, but the bundle
needs to be renamed and moved first.

The opennaas-luminis feature should possibly be split and renamed, but
for now I have put those bundles into a single feature.
Add Carlos to AUTHORS
Merge pull request #41 from gbehrmann/feature/refactor-feature-repositories

Feature/refactor feature repositories
Merge branch 'develop' into feature/configure-site-plugin

Conflicts:
	pom.xml