Add custom Interceptor chain for Linked, Validated, Secured

Introduce custom Intefceptor chain to workaround CDI 1.0 limitation
of having to redefine the interceptor chain configuration pr module
that use it.

With our custom chain we can rely on CDI to provide a Instance<X>
of our wanted Interceptor type dynamically based on what is deployed
rather then what is configured.

All modules now only define the interceptor for our interceptor
chain instead of the individual ones.
Add Filtering of Allow header on Resource @OPTIONS requests

We simply filter the allow header on state changing HTTP verbs
to hint to the User that; if you're not authorized you're not
allowed to perform POST, PUT, DELETE on given resource.

This is not security measure in it self, but rather a self
exploration hint.
Add Security to StateChanging REST methods

* POST, PUT, DELETE now require authentication
* Change to use Twitter Sign In, instead of app authentication
* Workaround AGOVA-53

When the Security Module is included in the deployment
all REST services are locked down. This means any state changing
methods will require authentication. The Security Module test-jar
comes with a Arquillian Extension that will setup do a full
authentication in AfterDeploy and setup RestAssured with a
valid Http Session. This allow the conference, user, attachment
REST Stories used as final functional tests in the Application
to work with our without the Security Module included. The REST
tests have no knowledge of the Security Module.

Issue: #52