Sessions expire in 90m instead of 2h as the counter suggests

[vec4]

PWD's newSession function spawns sessions for 90 minutes, but our timer on the page counts down for 2 hours. After 90 minutes are up, the console in the browser is not useable.

The 90 minutes parameter is encoded in the URL for the POST request in the PWD SDK under the createSession() function, which is called within the newSession routine. Since we are using the dist for the SDK, I think the only way to change this would be to create a wrapper that does the POST request ourselves or build the PWD SDK with our modifications and use that script. Another option is to override the parameter in the golang handler in PWC. Or we can change the client timer to match PWD. It is disappointing that this is not a configurable parameter on the PWD side though.