Make the session cookie work with the terminal

[Senyoret1]

Did you run make format && make check?
Yes

Fixes #248

Changes:

• Now the Path param, set in the hypervisor configuration file, is added to the session cookie. This makes the web browser start sending the session cookie to the terminal window while using the default config, as previously web browsers were sending the cookie only to the /api paths (default browser behavior if the Path param is not set). This makes the terminal work with https connections while auth is activated.

How to test this PR:
Open the full terminal using the manager while auth and tls are active. See note below.

[Senyoret1]

There is a small issue with this: if you use the manager without the change, the hypervisor will send a cookie without the path and the browser will save it; if you then add the changes, the hypervisor will send the new cookie with the path and the browser will send both cookies with every request, which will make the authentication process to fail. To solve this, erase the cookies on the browser or wait until the old cookie expires (I think it last something like 2 days)

[jdknives]

The intended change works as expected. I can successfully open the dmsgpty terminal with https when TLS is enabled. However, the overview page cannot be loaded because the uptime request fails:

2020/03/27 11:00:16 "GET https://localhost:8080/api/visors/02980b3933c56b68193efed1bb2f6438d20c381e0d34a29829ac91040d5e6f4a23/uptime HTTP/2.0" from 127.0.0.1:64574 - 500 59B in 877.671997ms

We recently changed the config name of the uptime tracker. Maybe merging latest changes from develop into your branch will solve this issue.