RA-379: Persist User session location

Added FragmentController to persist user session location
Corrected header.gsp to call SessionFragmentController
No. The quick summary is that we need the session context to work for multiple technology approaches, including if you aren't using the UI Framework module, and the client is pure JavaScript. That's why we have UiSessionContext extends SessionContext.

It's fine and good to have the location here, we just need to make sure that if it ever gets modified, we also modify the plain JS-safe id value.

Basically, just add the one additional line to what you already did here.