Faro should not create a new session when calling setSession() to only change attributes within a valid session

[codecapitano]

Why

When calling the setSession() to dynamically update session attributes, Faro always creates a new sessionId.
The session updater function shouldn't create a new sessionId if only attributes changed within a valid session.
A valid session is a session which neither reached the max lifetime or max inactivity time thresholds.

What

• setSession() should only auto create a new sessionId if a session is invalid or if the caller provided a new sessionId.