[AS7-6263] Allow expressions for management & vault core services

[AS7-6263] Allow expressions for management core service

* expand the support for expressions for management & vault core-service resources' attributes (see below for a comparison with AS7 7.1.2.Final model)
* add resource transformation to reject these expression for legacy version
=> for the attributes changed by this PR *and* other attributes that have allowed expressions since version 1.2.0 (ie AS7 7.1.2.Final)
* I'm not 100% confident in the location where I register the transformers. I do this in `HostModelUtil.registerHost()`. At first, I did it in `HostResourceDefinition.registerChildren()` but many tests fail in that case because the transformers are registered twice. The tests pass when the registration occurs in `HostModelUtil.registerHost()`

I did not test the core-service's resource transformation for legcay version. I'm working on that but if someone could at least review that the transformers registration looks correct...

    Enter legacy AS version: 7.1.2.Final

    ====== Comparing core models ======
    ====== Resource root address: [] - Current version: 1.4.0; legacy version: 1.2.0 =======
    --- Problems for relative address to root ["core-service" => "management","security-realm" => "*","authentication" => "ldap"]:
    Different 'expressions-allowed' for attribute 'advanced-filter'. Current: true; legacy: false
    Different 'expressions-allowed' for attribute 'base-dn'. Current: true; legacy: false
    Different 'expressions-allowed' for attribute 'recursive'. Current: true; legacy: false
    Different 'expressions-allowed' for attribute 'user-dn'. Current: true; legacy: false
    Different 'expressions-allowed' for attribute 'username-attribute'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'advanced-filter' of operation 'add'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'base-dn' of operation 'add'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'recursive' of operation 'add'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'user-dn' of operation 'add'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'username-attribute' of operation 'add'. Current: true; legacy: false
    --- Problems for relative address to root ["core-service" => "management","security-realm" => "*","authentication" => "local"]:
    Different 'expressions-allowed' for attribute 'allowed-users'. Current: true; legacy: false
    Different 'expressions-allowed' for attribute 'default-user'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'allowed-users' of operation 'add'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'default-user' of operation 'add'. Current: true; legacy: false
    --- Problems for relative address to root ["core-service" => "management","security-realm" => "*","authentication" => "plug-in"]:
    Different 'default' for attribute 'mechanism'. Current: "DIGEST"; legacy: undefined
    --- Problems for relative address to root ["core-service" => "management","security-realm" => "*","authentication" => "properties"]:
    Different 'expressions-allowed' for attribute 'path'. Current: true; legacy: false
    Different 'expressions-allowed' for attribute 'plain-text'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'path' of operation 'add'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'plain-text' of operation 'add'. Current: true; legacy: false
    --- Problems for relative address to root ["core-service" => "management","security-realm" => "*","authentication" => "truststore"]:
    Different 'expressions-allowed' for attribute 'keystore-path'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'keystore-path' of operation 'add'. Current: true; legacy: false
    --- Problems for relative address to root ["core-service" => "management","security-realm" => "*","authentication" => "users","user" => "*"]:
    Different 'expressions-allowed' for attribute 'password'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'password' of operation 'add'. Current: true; legacy: false
    --- Problems for relative address to root ["core-service" => "management","security-realm" => "*","authorization" => "properties"]:
    Different 'expressions-allowed' for attribute 'path'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'path' of operation 'add'. Current: true; legacy: false
    --- Problems for relative address to root ["core-service" => "management","security-realm" => "*","server-identity" => "ssl"]:
    Different 'expressions-allowed' for attribute 'alias'. Current: true; legacy: false
    Different 'expressions-allowed' for attribute 'keystore-path'. Current: true; legacy: false
    Different 'expressions-allowed' for attribute 'protocol'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'alias' of operation 'add'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'keystore-path' of operation 'add'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'protocol' of operation 'add'. Current: true; legacy: false
    --- Problems for relative address to root ["core-service" => "vault"]:
    Different 'expressions-allowed' for attribute 'code'. Current: true; legacy: false
    Different 'nillable' for parameter 'code' of operation 'add'. Current: true; legacy: false
    Different 'expressions-allowed' for parameter 'code' of operation 'add'. Current: true; legacy: false
    Different 'nillable' for parameter 'vault-options' of operation 'add'. Current: true; legacy: false