Replace the usage of AccountGeneralPreferences with a different class
in extension API package. Given that this is embedded entity in the
accounts table, only the columns are removed from the database, while
the accounts table itself is still preserved.
Bump database version, migrate the data from db to git and delete the
entity from the code. As the consequence the following columns from
accounts table are removed:
size_bar_in_change_table
maximum_page_size
relative_date_in_change_table
use_flash_clipboard
legacycid_in_change_table
diff_view
mute_common_path_prefixes
email_strategy
show_site_header
download_command
download_url
date_format
time_format
review_category_strategy
Previously GET and PUT REST handlers for user preferences mixed db and
git operations because parts of the preferences (my menu entries and
URL aliases) were alreay stored in git backend. Now that the whole data
is stored in git backend, caching mechanism is needed to not degrade the
performance when retrieving the user preferences on the server side in
different use cases, like sending mail etc. Use Account entity for this
and extend AccountCache implementation to load general user preferences.
Download-commands plugin must be updated, as it references the old
entity.
Change-Id: I35311539f73e0f7baeaedff779bc44c2f5b133f8
b06d2e33b2