hasSession-cache used regardless of SA Client ID change

[vetleaa]

Note: This issue is highly specific and I'm not sure you should fix it, but here goes

When two stacks on the same domain with separate SA Client IDs are navigated between, the hasSession-cache is kept (e.g. news.com and news.com/pluss).

The SDK never validates the Client ID stored in hasSession-cache against the running Client ID. This causes other values (SP_ID etc.) to be invalid until the cache expires. This can cause problems communicating with other services / APIs.

Also, I've made a manual workaround for my implementation, so don't worry about that 👍