Sync OSGi handling with Apache JClouds Project

This project, the aws-lab version of Apache JClouds, share the exact build instructions as the primary Apache JClouds project with all its modules.
Apache JClouds is shifting its strategy in handling OSGi configuration. Instead of using the Maven Bundle Plugin, a wrapper of the BND plugin, the BND plugin gets used directly.
- Remove the OSGi configuration from each module. The configuration gets served to the BND through dedicated configuration / bnd files.
- Onboard bnd-configuration files, one per module.

Ignore bnd files in rat plugin

apis/glacier/bnd.bnd

@@ -0,0 +1,2 @@
+Export-Package: \
+    org.jclouds.glacier.*;version="${project.version}";-noimport:=true

apis/glacier/pom.xml

@@ -32,7 +32,6 @@
   <artifactId>glacier</artifactId>
   <name>Apache jclouds :: AWS :: Glacier API</name>
   <description>jclouds components to access an implementation of glacier</description>
-  <packaging>bundle</packaging>
 
   <properties>
     <test.aws.identity>FIXME_IDENTITY</test.aws.identity>
@@ -42,8 +41,6 @@
     <test.glacier.build-version />
     <test.glacier.identity>${test.aws.identity}</test.glacier.identity>
     <test.glacier.credential>${test.aws.credential}</test.glacier.credential>
-    <jclouds.osgi.export>org.jclouds.glacier*;version="${project.version}"</jclouds.osgi.export>
-    <jclouds.osgi.import>org.jclouds*;version="${project.version}",*</jclouds.osgi.import>
   </properties>
 
   <repositories>