Proposal: use metapackage for jderobot-deps & jderobot-devs

# Proposal: use metapackage for jderobot-deps & jderobot-devs

Using described steps at http://jeffhoogland.blogspot.com.es/2011/08/howto-create-debian-meta-package.html, we can generate a metapackage with **no code**, so it targets to **all architectures**.
Therefore, make steps are no longer required.
## What it implies?

jderobot - Jderobot .deb as always (the only one with code)
jderobot-deps - binary dependencies of Jderobot
jderobot-deps-dev - headers of libraries
## Looping the loop

jderobot-dev-tools - for cmake, git, build-essential, pkg-config
jderobot-all - includes all above
## How it works
1. Just create a "fake" hierarchy
`mkdir -p pkg_name/DEBIAN/`
2. Fill it with .deb info (apt-cache show | dpkg --info)
`edit pkg_name/DEBIAN/control`
3. Build (create) package
`dpkg --build pkg_name`
## Pros and cons
- It is decoupled to jderobot code
- (pro) jderobot forget requirements for cpack
- (cons) metapackage can become deprecated (out-of-sync)
- No more embedded into cpack
- Requires explicit command line execution
## Remember

Use `Architecture: all`, so it works for any target ;)

Since these _metapackages_ are fake ones, and gather all required dependencies, push it here could be a good idea. (It's only text, so have it in git will increase commodity and clarity).