cookies: only consider full path matches

I found a bug which cURL sends cookies to the path not to aim at.
For example:
- cURL sends a request to http://example.fake/hoge/
- server returns cookie which with path=/hoge;
  the point is there is NOT the '/' end of path string.
- cURL sends a request to http://example.fake/hogege/ with the cookie.

The reason for this old "feature" is because that behavior is what is
described in the original netscape cookie spec:
http://curl.haxx.se/rfc/cookie_spec.html

The current cookie spec (RFC6265) clarifies the situation:
http://tools.ietf.org/html/rfc6265#section-5.2.4
Path match fail.
If set-cookie path has end of '/', it can not match url path without '/'.
RFC6265 5.1.4 says
----------
4. Output the characters of the uri-path from the first character up
   to, but not including, the right-most %x2F ("/").
----------
but, for example, URL path /hoge?fuga=xxx means /hoge/index.cgi?fuga=xxx in some site without redirect.
Ignore this algorithm because /hoge is uri path for this case(uri path is not '/').

So cURL struct Cookie keeps path without end of '/' then do path match.