fix: a little session buffering logic

[pauldambra]

Trying to intuit my way to understanding what is happening with the session buffering.

Logically we can (when there is a minimum duration set):

• have a buffer with data and a session id assigned
• and then the session id changes
• we would then compare the buffer's data timestamp
• with the new session start timestamp
• which would give us a negative duration
• this would never meet the minimum test
• and we would never flush that buffer

Let's make sure that doesn't happen

[github-actions]

Size Change: +40 B (0%)

Total Size: 733 kB

Filename	Size	Change
dist/array.full.js	174 kB	+10 B (0%)
dist/array.js	115 kB	+10 B (0%)
dist/es.js	115 kB	+10 B (0%)
dist/module.js	115 kB	+10 B (0%)

ℹ️ View Unchanged

Filename	Size
dist/exception-autocapture.js	12 kB
dist/recorder-v2.js	104 kB
dist/recorder.js	58.3 kB
dist/surveys.js	39.8 kB

_{compressed-size-action}