ngCookies Provide an option of not encoding cookie value for $cookies.put

[kamarouski]

For some scenarios we need to access a raw cookie rather than encoded one. This is especially important when dealing with legacy systems that relies on unencoded cookie values.

[Narretz]

Given that the cookieWriter isn't awfully complicated, and this is not a very common requirement, it gets a -1 from me.

[YuraDubensky]

+1 from me. When cookie data is consumed by server (i.e. serialized json object), it brings additional complications.

[chancez]

The existing behavior is fairly surprising and undocumented honestly. It took me a good while to debug why my content was being double url encoded. I thought it might be my server component doing something crazy, but it was because I was URL encoding my value before using $cookies.put, and it was even harder to debug because $cookies.get was showing me the same value I was putting, but thats because it does decoding on retrieval as well.

[Narretz]

PRs for documenting this behavior are welcome!