BREAKING CHANGE: Refactor URL encoding/decoding and string types

[christopherthielen]

The URL parsing code currently has some vestiges from when it only worked with the angular 1 $location service.

The ng1 $location service has one major flaw we could never work around. This was the reason the custom ~2F encoding was created (when encoding parameter values with slashes in them).

Goals:

• ui-router-core should not have special handling for encoding slashes
• angular-ui-router itself should encode slashes as ~2F
  • only in path parameter values
  • The string type currently process ~2F; rename this type to path and make it the default parameter type for path parameters in ng1 only
• Move LocationService and LocationConfig from coreservices to UIRouter instance

BREAKING CHANGE

1. Slashes in param values no longer encode to ~2F except for ng1 path params
2. coreservices.location moved to UIRouter.location.service and UIRouter.location.config