Fix: Set the correct OOM event timestamp

[kevinrenskers]

📜 Description

Use the last breadcrumb's timestamp as the OOM event timestamp

💡 Motivation and Context

Fixes #2383

💚 How did you test it?

Unit tests, and ran the sample app, creating an OOM and waiting a few minutes before starting the app again. The OOM event has the correct timestamp: https://sentry.io/organizations/sentry-sdks/issues/2291658301/?project=5428557&query=is%3Aunresolved&referrer=issue-stream.

📝 Checklist

• I reviewed the submitted code
• I added tests to verify the changes
• I updated the docs if needed
• Review from the native team if needed
• No breaking changes

🔮 Next steps

[philipphofmann]

LGTM

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	1225.90 ms	1247.62 ms	21.72 ms
Size	20.75 KiB	374.39 KiB	353.64 KiB

Baseline results on branch: master

Startup times

Revision	Plain	With Sentry	Diff
09ad77e	1242.14 ms	1244.02 ms	1.88 ms
6177f2d	1206.55 ms	1226.20 ms	19.65 ms
347a8e9	1243.50 ms	1265.90 ms	22.40 ms
ef8b0ce	1212.34 ms	1249.64 ms	37.30 ms
8607e67	1213.53 ms	1238.20 ms	24.67 ms
0fdf0b2	1249.20 ms	1254.08 ms	4.88 ms
5025d2e	1245.14 ms	1268.58 ms	23.44 ms
ee127f4	1203.49 ms	1231.28 ms	27.79 ms
2ce5819	1258.02 ms	1271.94 ms	13.92 ms
c2a9b60	1222.10 ms	1240.62 ms	18.52 ms

App size

Revision	Plain	With Sentry	Diff
09ad77e	20.50 KiB	339.01 KiB	318.51 KiB
6177f2d	20.51 KiB	332.90 KiB	312.40 KiB
347a8e9	20.51 KiB	333.16 KiB	312.65 KiB
ef8b0ce	20.50 KiB	337.71 KiB	317.20 KiB
8607e67	20.50 KiB	338.99 KiB	318.49 KiB
0fdf0b2	20.51 KiB	332.90 KiB	312.39 KiB
5025d2e	20.51 KiB	331.79 KiB	311.28 KiB
ee127f4	20.51 KiB	333.10 KiB	312.59 KiB
2ce5819	20.50 KiB	337.76 KiB	317.26 KiB
c2a9b60	20.50 KiB	333.54 KiB	313.04 KiB

Previous results on branch: fix/2383-use-correct-OOM-timestamp

Startup times

Revision	Plain	With Sentry	Diff
92b8904	1240.35 ms	1273.40 ms	33.06 ms

App size

Revision	Plain	With Sentry	Diff
92b8904	20.75 KiB	374.39 KiB	353.64 KiB