ISPN-3514 Align XML configuration between Server and Embedded* The objective is for server configuration to be readable by embeddedand viceversa.* Those elements that are not relevant for embedded configuration areignored and highlighted with an INFO message.* All configuration affecting test results has been adjusted.* This commit does not include changes to demos, documentation orschema files. This will come later, once the XML has been fully agreed.* If there's any testing XML that has not been converted, it's becauseit's not being tested at all, it should be removed in the cleanup phase.* During the cleanup phase, all unused attributes/elements and parserswill be removed.* The XML in general follows the pattern used by server which meansthat there are some noticeable changes to the way embedded XML isconfigured:* Cache mode is now part of the cache definition, i.e. local-cache,distributed-cache...etc.* Default cache is now specified at the cache container level, namingit.* Shutdown hook now configured as an attribute of cache instead ofa separate element.* X-Site local site derived from transport's site-id, instead of addingyet another xml configuration option.* Compatibility mode drops enabled attribute, element being presentenables it.* Same thing happens with versioning, element being present enables it.* Deadlock detection's spin duration used to enable/disable it. Ifconfigured with a value below 0, it's disabled.* unsafe.unreliableReturnValues is now configured via an attributeinstead of a separate element.* store-as-binary is disabled by making sure keys and values are bothset to false.* L1 is disabled by making its lifespan -1.* Replication queue configured via cache level attributes, and it'sdisabled by making the queue size negative.* Simplified thread pool configuration by avoiding to leak XMLconfiguration details into programmatic API. In the programmaticversion, just provide factories.* Fixed thread pool injection in server.