run tools/reorder_message_file.py on the mes files

(This is a test of new git server :)

src/bin/dhcp4/dhcp4_messages.mes

@@ -44,10 +44,6 @@ name was malformed or due to internal server error.
 A debug message listing the command (and possible arguments) received
 from the Kea control system by the DHCPv4 server.
 
-% DHCP4_CONFIG_RECEIVED received configuration %1
-A debug message listing the configuration received by the DHCPv4 server.
-The source of that configuration depends on used configuration backend.
-
 % DHCP4_CONFIG_COMPLETE DHCPv4 server has completed configuration: %1
 This is an informational message announcing the successful processing of a
 new configuration. It is output during server startup, and when an updated
@@ -68,6 +64,10 @@ This warning message is issued on an attempt to configure multiple options
 with the same option code for a particular subnet. Adding multiple options
 is uncommon for DHCPv4, but is not prohibited.
 
+% DHCP4_CONFIG_RECEIVED received configuration %1
+A debug message listing the configuration received by the DHCPv4 server.
+The source of that configuration depends on used configuration backend.
+
 % DHCP4_CONFIG_START DHCPv4 server is processing the following configuration: %1
 This is a debug message that is issued every time the server receives a
 configuration. That happens at start up and also when a server configuration
@@ -147,6 +147,11 @@ point, the setting of the flag instructs the server not to choose a
 subnet, an action that severely limits further processing; the server
 will be only able to offer global options - no addresses will be assigned.
 
+% DHCP4_INIT_FAIL failed to initialize Kea server: %1
+The server has failed to initialize. This may be because the configuration
+was not successful, or it encountered any other critical error on startup.
+Attached error message provides more details about the issue.
+
 % DHCP4_INVALID_ADDRESS_INIT_REBOOT invalid address %1 requested by INIT-REBOOT client (id: %2, hwaddr: %3)
 This debug message is issued when the client being in the INIT-REBOOT state
 requested an address which is not assigned to him. The server will respond
@@ -332,11 +337,6 @@ A debug message listing the data returned to the client.
 The DHCPv4 server has encountered a fatal error and is terminating.
 The reason for the failure is included in the message.
 
-% DHCP4_INIT_FAIL failed to initialize Kea server: %1
-The server has failed to initialize. This may be because the configuration
-was not successful, or it encountered any other critical error on startup.
-Attached error message provides more details about the issue.
-
 % DHCP4_SHUTDOWN server shutdown
 The DHCPv4 server has terminated normally.
 

src/bin/dhcp6/dhcp6_messages.mes

@@ -40,10 +40,6 @@ address assignment.  The most likely cause is a problem with the client.
 A debug message listing the command (and possible arguments) received
 from the Kea control system by the IPv6 DHCP server.
 
-% DHCP6_CONFIG_RECEIVED received configuration: %1
-A debug message listing the configuration received by the DHCPv6 server.
-The source of that configuration depends on used configuration backend.
-
 % DHCP6_CONFIG_COMPLETE DHCPv6 server has completed configuration: %1
 This is an informational message announcing the successful processing of a
 new configuration. it is output during server startup, and when an updated
@@ -64,6 +60,10 @@ This warning message is issued on an attempt to configure multiple options with
 same option code for the particular subnet. Adding multiple options is uncommon
 for DHCPv6, but it is not prohibited.
 
+% DHCP6_CONFIG_RECEIVED received configuration: %1
+A debug message listing the configuration received by the DHCPv6 server.
+The source of that configuration depends on used configuration backend.
+
 % DHCP6_CONFIG_START DHCPv6 server is processing the following configuration: %1
 This is a debug message that is issued every time the server receives a
 configuration. That happens start up and also when a server configuration
@@ -245,6 +245,12 @@ subnet, an action that severely limits further processing; the server
 will be only able to offer global options - no addresses or prefixes
 will be assigned.
 
+% DHCP6_INIT_FAIL failed to initialize Kea server: %1
+The server has failed to establish communication with the rest of Kea,
+failed to read JSON configuration file or excountered any other critical
+issue that prevents it from starting up properly. Attached error message
+provides more details about the issue.
+
 % DHCP6_LEASE_ADVERT address lease %1 advertised (client duid=%2, iaid=%3)
 This debug message indicates that the server successfully advertised
 an address lease. It is up to the client to choose one server out of the
@@ -511,12 +517,6 @@ to recover.
 The IPv6 DHCP server has encountered a fatal error and is terminating.
 The reason for the failure is included in the message.
 
-% DHCP6_INIT_FAIL failed to initialize Kea server: %1
-The server has failed to establish communication with the rest of Kea,
-failed to read JSON configuration file or excountered any other critical
-issue that prevents it from starting up properly. Attached error message
-provides more details about the issue.
-
 % DHCP6_SHUTDOWN server shutdown
 The IPv6 DHCP server has terminated normally.