It is not default — it is base.

Do not add default default profile if there is at least on bundled/custom global profile — as before.

use correct serialization implementation in the copyProfile – otherwise when modifiable model of scheme is created, lazy loaded element data is not used (and as result, locked attribute is not correctly set)

testPreserveCompatibility is removed because we not DO NOT TOUCH files unless it is really modified In production we "do not preserve compatibility" (flag) since spring 2016

CompletableFuture requires us to explicitly add catch handler to avoid error swallow — but our Promise automatically logs error if no catch handler
(cherry picked from commit 78c1814)

(cherry picked from commit 3ab9396)

load inpection profiles in pooled thread

ProjectInspectionProfileManagerImpl — isUseOldFileNameSanitize because directory based storage uses strict sanitize, but scheme manager non-strict

enable saving.state.in.new.format.is.allowed