[2025] Rename message id and description

This is done so there is no misunderstanding about whether b10-auth is
processing NOTIFYs.

src/bin/auth/auth_messages.mes

@@ -110,8 +110,8 @@ look into the cause and address the issue.  The log message includes
 the client's address (and port), and the error message sent from the
 lower layer that detects the failure.
 
-% AUTH_PROCESS_NOTIFY processing incoming NOTIFY for zone name %1, zone class %2
-This is a debug message reporting that an incoming NOTIFY is being processed.
+% AUTH_RECEIVED_NOTIFY received incoming NOTIFY for zone name %1, zone class %2
+This is a debug message reporting that an incoming NOTIFY was received.
 
 % AUTH_NOTIFY_QUESTIONS invalid number of questions (%1) in incoming NOTIFY
 This debug message is logged by the authoritative server when it receives

src/bin/auth/auth_srv.cc

@@ -828,7 +828,7 @@ AuthSrvImpl::processNotify(const IOMessage& io_message, Message& message,
         return (false);
     }
 
-    LOG_DEBUG(auth_logger, DBG_AUTH_DETAIL, AUTH_PROCESS_NOTIFY)
+    LOG_DEBUG(auth_logger, DBG_AUTH_DETAIL, AUTH_RECEIVED_NOTIFY)
       .arg(question->getName().toText()).arg(question->getClass().toText());
 
     const string remote_ip_address =

tests/lettuce/features/xfrin_notify_handling.feature

@@ -20,7 +20,7 @@ Feature: Xfrin incoming notify handling
 
     When I send bind10 with cmdctl port 47804 the command Xfrout notify example.org IN
     Then wait for new master stderr message XFROUT_NOTIFY_COMMAND
-    Then wait for new bind10 stderr message AUTH_PROCESS_NOTIFY
+    Then wait for new bind10 stderr message AUTH_RECEIVED_NOTIFY
     Then wait for new bind10 stderr message ZONEMGR_RECEIVE_NOTIFY
     Then wait for new bind10 stderr message XFRIN_XFR_TRANSFER_STARTED
     Then wait for new bind10 stderr message XFRIN_TRANSFER_SUCCESS not XFRIN_XFR_PROCESS_FAILURE