Migrate project config to global config. Remove option to create Project-level configs

Description

All configuration should be stored on global level. First, we have to migrate project config to global level following these rules:

Migrate to global level if different from default.If global level already exists for project. Merge it.If global level already exists for project but it is related with many projects. Extract it to new global config. Merge it.

Ideas how to do that:

  1. Liquibase migration - it would be best to perform it as a single SQL migration runned immediately when new app version is started. However, due to convoluted nature of operations that need to be performed, this may be hard to achieve.

  2. If the former is not possible, we will need a code that will handle both new and old configuration + migration job. After running the migration job, we can safely remove parts of the code refering to the old config.

Finally, we should remove button to create Project level config. In both cases we should do this as soon as possible.

Linked issues

relates to
Issue Type Icon ESFC-720 Remove space-level config Priority: Lowest Assignee:
Backlog
is blocked by
Issue Type Icon ESFJ-780 Add “Default shared fields (shared issue)”, “Default filter columns (shared filter)” to global config Priority: Medium Assignee:
Released