Jersey 2469

As UriBuilder spec defines, query parameters should be encoded using application/x-www-form-urlencoded rules (https://jax-rs-spec.java.net/nonav/2.0-SNAPSHOT/apidocs/javax/ws/rs/core/UriBuilder.html).

Changed UriComponent to conform to UriBuilder spec, making query parameter to be encoded correctly on three methods of UriBuilder (queryParam(...), replaceQueryParam(...), replaceQuery(...)).

Added new unit test to verify correct encoding of special characters, and adjust existent test to expect values encoded in query string. 

This set is expected to be encoded when used in query string: ! # $ & ' ( ) * + , / : ; = ? @ [ ];
 as defined in (http://en.wikipedia.org/wiki/Percent-encoding).

Check (https://java.net/jira/browse/JERSEY-2469 and https://java.net/projects/jersey/lists/users/archive/2014-04/message/13).
I interpreted differently that spec. The application/x-www-form-urlencoded spec says 
> "reserved characters are escaped as described in [RFC1738], section 2.2"; 

that seems to mean that all reserved characters should be encoded, whether the text to encode is a query param or an html form post. The set of reserved characters is somehow defined in that spec and more precisely defined on RFC 3986 (which is an update of the RFC 1738). That was mainly the reason for encoding those other chars.
Said that, I reasearched againg and took a closer look at other implementations on the JDK and the spec on www.whatwg.org; and I saw that the pull request changes are more restrictive than the specs for URLEncoder (http://docs.oracle.com/javase/7/docs/api/java/net/URLEncoder.html) that are the same as http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#application/x-www-form-urlencoded-encoding-algorithm. In particular, the `*` character should not be encoded based on that latter specs.
I think that we should make the behavior of the application/x-www-form-urlencoded encoding for query param in the UriBuilder implementation, the same as the URLEncoder current implementation. I can make a small change on this PR to align to that.
*What do you think Marek? Is that a correct direction for this?*

(Just to note, I found this issue when creating urls that would be used on different browsers; particularly on Safari the urls generated where failing, and after manually encoding some portions of the query, the urls started to work)