Restore the log-and-continue handling of NotFoundException on decode

Rethrowing the NotFoundException as MALException changed the behavior of
a long-standing path: callers above may push the error back to consumers
or brokers that previously carried on after the logged warning. Keep the
original swallowing behavior; the repeated-read guard still reports a
descriptive MALException instead of an NPE when a previous decode
attempt has failed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: CesarCoelho

transports/transport-generic/src/main/java/esa/mo/mal/transport/gen/body/LazyMessageBody.java

@@ -283,10 +283,6 @@ protected synchronized void decodeMessageBody() throws MALException {
         } catch (NotFoundException ex) {
             Transport.LOGGER.log(Level.WARNING,
                     "(2) Unable to decode the Message Body!", ex);
-            // Propagate instead of swallowing: otherwise messageParts stays
-            // null and readers fail later with an NPE that hides this cause
-            throw new MALException("Unable to decode the Message Body! "
-                    + "The operation could not be found!", ex);
         }
     }