Adds the ability to stop and resume sessions. This prevents the handled/unhandled error count from
incrementing when a session is in the stopped state, which may be desirable if a user manually
tracks sessions and does not care about crashes that occur in the background.

when a session is stopped, no session information should be present in error payloads.

…ssion information in their payl

Allow sessions to be stopped on the NDK. when a session is stopped from the java layer, the session
information will no longer be serialised in the error payload of fatal NDK errors.

the START_SESSION message is emitted when a session is started or resumed, and allows the NDK layer
to update its cached value for session information which is included in the error payload. It was
previously assumed that the handled count would always be 0 when starting a session - this is no
longer the case as sessions can be resumed, therefore the handled count is passed as part of the
message.

…ng sessions

…ining method

Support stopSession() and resumeSession() in NDK

Add mazerunner scenarios for stopping/resuming a session

Wait for session scenarios to send session before crashing

Add stopSession() and resumeSession() to Client