replace Cookie.js/cookieManager with dojo.cookie. Some things to watch out for as...

replace Cookie.js/cookieManager with dojo.cookie.  Some things to watch out for as we review this changeset:

In Cookie.js, a -1 passed as the expires parameter indicated a session cookie.  We could also specify such things as "+1y" or a specific date.  With dojo.cookie, an expires value of -1 deletes a cookie.  Not specifying an expires option will create a session cookie.  We can enter a date or a number days from today.  For the case in the code where we had "+1y", I supplied a value of 365.

In the previous code, we used empty strings for a lot of cookie deletion.  The canonical dojo example has us using null (with an expires of -1).  There were also some cases where it seemed obvious that we were deleting cookies, but were at the same passing an actual value (see base.js).  I changed these to nulls.

In opac_utils.js, grabFleshedUser(), I fixed a dead code path where a cookie deletion attempt came after a return statement.

I ran through the opac within and outside of the staff client, tried all of the acquisition UI's from the Acq menu, and most of the interfaces under Admin, and didn't find any auth cookie errors.

git-svn-id: svn://svn.open-ils.org/ILS/trunk@18687 dcc99617-32d9-48b4-a31d-7c20da2025e4