[SPIKE] Figure out how to prepopulate the database with all languages

[PaulKlauser]

Currently the database is initially populated with whatever the current language is when the app is first launched. Subsequent launches will not repopulate, regardless of the language.

This is due to the implementation relying on an initial set of string resources that are shoved into the database on first launch in PresetsRepository#populateDatabase().

Should we instead prepopulate the database like: https://developer.android.com/training/data-storage/room/prepopulate

Or is that too much of a compromise with how Crowdin supplies our translations?

We could likely check for language changes and repopulate the database, but the complexity that opens up seems like it may not be worth the effort.

Outcome of this spike should be story(s) for implementing whatever strategy is decided to get our database populated in a way that:

• properly supports multiple languages
• minimizes pain during migrations
• allows flexibility in adding new preset phrases with new versions of the app.

[PaulKlauser]

It does look like you can reference the language resources in other locale configurations, but we'd still need to iterate through all of the locales we support, and keep that in sync with the resource directories. Doesn't seem ideal, but it is one approach we could take.