feat: add remnant events migration plugin

[liuyang1520]

Summary

This PR adds a remnant events migration plugin to send the remnant events in Sqlite generated by old Android Java SDK, including:

• DB utils for retrieving the entries in sqlite database
• Covert the event to new format
• Send the event with this new Kotlin SDK

Todos:

• Remove events from sqlite after tracking with new SDK
• Add unit tests
• Create a confluence page for how to test this: https://amplitude.atlassian.net/wiki/spaces/GOV/pages/94437526/Android#How-to-test-both-old-and-new-Android-SDK-together

Checklist

• Does your PR title have the correct title format?
  yes
• Does your PR have a breaking change?:
  no

[secure-code-warrior-for-github]

Micro-Learning Topic: SQL injection (Detected by phrase)

Matched on "Sqli"

What is this? (2min video)

This is probably one of the two most exploited vulnerabilities in web applications and has led to a number of high profile company breaches. It occurs when an application fails to sanitize or validate input before using it to dynamically construct a statement. An attacker that exploits this vulnerability will be able to gain access to the underlying database and view or modify data without permission.

Try this challenge in Secure Code Warrior

[falconandy]

1. Migration logic is changed to write legacy data directly to new storages.
2. Migration logic is moved from Plugin to let run it before any plugins including standard plugin (AndroidContextPlugin, etc). I called it Initializer but maybe simple configuration flag like runLegacyDataMigration is enough. Reason: device/user id logic is pretty complex (classes State, IdentityContainer, IdentityListener, etc) and asynchronous - AndroidContextPlugin concurrently sets random device id on first run if device id is currently empty - sometimes the random value wins, sometimes - value from legacy data wins (if migration logic is implemented in a plugin executed after AndroidContextPlugin).
3. Supported: on first run since upgrade (recommended) - device/user id, session id, last event date/id, events, identifies, intercepted identifies. If migration was enabled later after upgrade - only events are migrated.
4. Supported sqlite db versions - v3 (2015 year) and current v4 (2/9/23, added table identify_interceptor)
5. Added support for instance names.
6. Some legacy fields are converted to new names/format: library -> from object to string, timestamp -> time, adid, android_app_set_id.
7. Added methods getUserId()/ getDeviceId to android Amplitude
8. After migration legacy sqlite data are cleaned except deviceId/userId - maybe they will be required later to link legacy/new ids, for example.
9. Added tests for v3/v4 sqlite databases - currently cover on first run since upgrade case

@justin-fiedler

Can you please add so extra tests around deviceId to verify that deviceId generated once and is persisted across multiple sessions correctly.

Not added yet.

[justin-fiedler]

Looks great. Thanks @falconandy!

[github-actions]

🎉 This PR is included in version 1.9.0 🎉

The release is available on:

• GitHub release
• v1.9.0

Your semantic-release bot 📦🚀