Summary
Currently we're only setting customer data on logs when a customer has an active session.
This misses out on headless and admin errors, as well as customer data on exceptions.
Result
This PR attempts to add the user type and user id with the usercontext.
Then it will attempt to get user data from the admin and user session itself
For some reason the admin gets forced to log out when the console is open in chrome
This happens when interacting with the admin session in ANY way, getData, isLoggedIn, hasUser
Summary Currently we're only setting customer data on logs when a customer has an active session. This misses out on headless and admin errors, as well as customer data on exceptions.
Result This PR attempts to add the user type and user id with the usercontext. Then it will attempt to get user data from the admin and user session itself