Instead of repeating the same if/else check on the error type when setting up the background message, move this in to BackgroundMessageView.
Provide different `setup()` variants, including one that just takes a throwable and a handler, and figures out the correct drawables and error message.
Update and simplify call sites.
This can happen if the edit history has not been propogated to the user's server.
If the edit history is missing then show an error with a link to the specifc Mastodon issue.
Fixes#3743
* 3408: First draft of help message on empty home timeline
* 3408: Move image spanning to utils; tweak gui a bit (looks like status)
* 3408: Use proper R again; appease linter
* 3408: Add doc; remove narrow comment
* 3408: null is default
* 3408: Add German text
* 3408: Stack refresh animation on top of help message (reorder)
* Add new Elephant Friend images. Use them in ListsActivity.
* Add error images to AccountListFragment
* Add error images to Timeline & Notifications fragment. Needs rework.
* Introduce BackgroundMessageView. Use it in AccountList.
* Use correct button style for BackgroundMessageView
Co-Authored-By: charlag <charlag@tutanota.com>
* Use BackgroundMessageView
* Add BackgroundMessageView docs
* Re-color and document elephants
* Apply feedback, disable refresh when error is shown
* Fix string typo