Use consistent device ID for multi process apps

[fractalwrench]

Goal

This changeset makes the notifier use a consistent device ID for apps which initialize Bugsnag in multiple processes. This is achieved by storing the device ID in a single file location which can be accessed concurrently from each process and is protected by a FileLock.

Changeset

• Created DeviceIdStore which is responsible for loading/saving the device ID to the file system
• Guarded the device ID file with a FileLock to prevent concurrent access in multiple processes, and a ReadWriteLock to prevent concurrent access from multiple threads.
• Updated the Client to persist a device ID to a file and to migrate any existing device ID from SharedPreferences or generating a random UUID if none already exists
• Created SharedPrefMigrator which reads legacy information from SharedPreferences. A separate PR will build on this by making this class read user information too, and delete the SharedPreferences file once the migration is complete
• Removed responsibility for storing the device ID from UserRepository
• Updated SynchronizedStreamableStore to use buffered IO

Testing

Added unit test coverage for new classes, and to verify that a file lock is used. Relied on existing E2E test coverage for regression testing, and also manually tested to verify that the device ID is stored in the new location.

[bugsnagbot]

Android notifier sizes

Format	Size impact of Bugsnag (kB)	Size impact of Bugsnag when Minified (kB)
APK	1444.76	1361.31
arm64_v8a	373.35	287.33
armeabi	352.86	266.84
armeabi_v7a	336.49	250.47
x86	410.2	328.28
x86_64	393.82	307.8

Generated by 🚫 Danger

[tomlongridge]

Is there good cause to catch Throwable here? I would be keen to avoid this and catch more specific errors as we don't catch throwables elsewhere in the codebase. (Also the catch in persistNewDeviceUuid is dong the same an so seem redundant.)