Updated our build to use Zinc artifacts

* Updated our build to use the Zinc artifacts built and published by dbuild.  The
main advantage is that we no longer need to build and publish the Sbt artifacts
(which are exactly the same used by Zinc) that are used in the Scala IDE for
incremental compilation.
(cherry picked from commit 6d40a3cd657cb4c5c895fd00946175198f6fcb9b)

* No need to put the sbt version number in the bundle name
(cherry picked from commit 5763bb8ca71dba39e9d927825cb3e33af1e571e8)

* Lifed up version for Sbt bundles in variable ${sbt.osgi.version}
(cherry picked from commit 65306fdb1d613a60f2080ce5c71d4f8efef901ab)
No reason for putting the manifest in the ${basedir}

The one single reason for doing it is to allow to import in the workspace the
`sbt.full.library` project, so that it can be correctly consumed by the
dependent projects (e.g., the `core project). However, given we practically
never had to do so in the past 6 months, it feels reasonable to remove the
flexiblity in the name of a cleaner build. In case you will need to import he
`sbt.full.library` project in Eclipse at any point, just create the required
.classpath and .project, and copy/paste in the project's root the META-INF
folder generated by the build (look in the target/ folder). Make  sure to do
the same for the `sbt.compiler.interface` project.
(cherry picked from commit e8a341020fadae2721dd9974b4bc9cb7a3215f11)
Adding organisation information in the POM to reduce duplication

In fact, the default value for Bundle-Vendor is ${pom.organization.name}
(cherry picked from commit 1103501f770a97e84a7ae544843772d71adee65c)
Deleted unneeded import-package clauses in toolchain MANIFESTs

The maven build does no longer spits out warnings for unused package imports in MANIFESTs.
(cherry picked from commit 73315a1febb18e9f4185045ea00ffd48c2b1026c)
Updated 2.10.x profile to use Scala 2.10.3-SNAPSHOT