making possible to override environment variables by system properties

When we are deploying in an environment like Amazon, we may need to update an environment variable on demand. Nowadays, we need to change the `environment.properties` in order to make this happen.

This pull request, allow us to override this properties using system properties.

We only allow user's to override properties that exists in `environment.properties` and do not allow to define only in system property.

```
#environment.properties
my.prop hello
```
```
//System.setProperty("my.prop", "bye");
environment.get("my.prop"); //bye
//System.setProperty("not.in.properties", "foo")
environment.get("not.in.properties"); //throw NoSuchElementException
```
Take it easy @garcia-jj. Already understood.

On Tuesday, November 11, 2014, Otávio Garcia <notifications@github.com>
wrote:

> In vraptor-core/pom.xml:
>
> > @@ -63,6 +63,12 @@
> >  			<artifactId>xstream</artifactId>
> >  			<version>1.4.7</version>
> >  		</dependency>
> > +		
>
> Yes, use @csokol <https://github.com/csokol> suggestion. We can't add a
> new jar with a lot of classes only because one method.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/caelum/vraptor4/pull/875/files#r20165131>.
>