Make app start profiling work in tests

[stefanosiano]

added a new content provider that writes app start profiling options to a config file to make the SDK think it was already initialized.
This way app start profiling will work the first time the app is started, too, like in tests.
Fixes #134

[sdzhong]

Hey @stefanosiano, Is the expectation for this PR that the com.example.vu.android.ThirdPartyContentProvider.onCreate() frame should appear as per this comment (its transaction)?

Do we have any sample EmpowerPlantActivity transactions for me to refer to with this PR, or does the aforementioned transaction work as a reference?

[stefanosiano]

@sdzhong sure, this is a transaction example and here is the associated profile
Yes, the expectation is to see com.example.vu.android.ThirdPartyContentProvider.onCreate() in the profile

[sdzhong]

Validated:

1. Flagship Error
2. Flagship Error’s Transaction
3. Flagship Transaction
4. Performance Issues - DB on Main Thread, File IO on Main Thread, Regex on Main Thread, Image Decoding on Main Thread, JSON Decoding on Main Thread