Make server configuration element order independent

Currently the ServerConfigurationParser reads elements in a specific order. This worked well for xml configuration when it was possible to define this requirement as part of the accompanying .xsd file.

However, in JSON and YAML the order of elements is not preserved/guaranteed in objects. Consequently, when using third party tooling it's possible for the json/yaml element order to be changed. Such transformations result in the server failing to start up when using the transformed configuration files.

This directly impacts the Infinispan Helm Charts The configuration YAML passed to the .Values file at chart install time is transformed when k8s templates are processed, changing the order, resulting in server startup failing.