Extract database module

[GianpaMX]

Resolves #1370 by extracting the database code into a separate gradle module

                       ┌─────┐
                       │ app │
                       └──┬──┘
                          │
        ┌─────────────────┼──────────────────────────┐
        │                 │                          │
        ▼                 ▼                          ▼
  ┌──────────┐   ┌───────────────────┐   ┌────────────────────┐
  │ database │   │ icon-pack-classic │   │ icon-pack-material │
  └─────┬────┘   └───────────────────┘   └────────────────────┘
        │
        ▼
   ┌────────┐
   │ crypto │
   └────────┘

There few tricks I had to do to extract the code:
IconPackChooser. I had to extract an interface (InterfaceIconPackChooser open to a better name suggestion) so the database module can depend on the interface but not on the implementation that requires values from the app BuildConfig

Exceptions. Instead of passing a string id, I just identified the exception class and linked it manually

Templates. Default name, fields and title are passed as strings instead of res ids

In a different PR

• publish crypto module in maven repo
• publish database module in maven repo

KeePassDX development can continue with the proposed structure and it should be familiar to any other developer

[J-Jamet]

OK, I have done a first check pass, there are things to improve:

• The database module must be self-sufficient
• It is sufficient to import only the database module into the app module. The crypto module is only known from database.
• The database module must not have access to the PreferenceManager
• The database module should be seen as a minimalist library, no unused imports
• Utility classes should not be in multiple locations
• App.Database package contains room db to manage URI so nothing to do with database module
  I am improving the code in the feature/Module_Refactoring

[J-Jamet]

I am refactoring and studying your code, there is one rule: never duplicate the code. You did it several times for the utilities. There is always a way to encapsulate without duplicating.

[J-Jamet]

I made only one enum for CompressionAlgorithm to avoid mapping