chore: fix nargo fmt formatting in aztec-nr (#22444)

## Summary
Fixes the `nargo fmt --check` failure on the backports PR #22441.

The comment in
`noir-projects/aztec-nr/aztec/src/messages/processing/mod.nr` exceeded
the line width limit, causing the formatter to reject it.

## Test plan
- CI `nargo fmt --check` should pass on the backports PR after this is
merged into `backport-to-v4-next-staging`

ClaudeBox log: https://claudebox.work/s/e09a3592270d40e2?run=1

Author: Thunkar

noir-projects/aztec-nr/aztec/src/messages/processing/mod.nr

@@ -164,8 +164,9 @@ pub(crate) unconstrained fn get_pending_partial_notes_completion_logs(
 ) -> EphemeralArray<Option<LogRetrievalResponse>> {
     let log_retrieval_requests = EphemeralArray::at(LOG_RETRIEVAL_REQUESTS_ARRAY_BASE_SLOT);
 
-    // We create a LogRetrievalRequest for each PendingPartialNote in the EphemeralArray. Because we need the indices in
-    // the request array to match the indices in the partial note array, we can't use EphemeralArray::for_each, as that
+    // We create a LogRetrievalRequest for each PendingPartialNote in the EphemeralArray. Because we need the indices
+    // in the request array to match the indices in the partial note array, we can't use EphemeralArray::for_each, as
+    // that
     // function has arbitrary iteration order. Instead, we manually iterate the array from the beginning and push into
     // the requests array, which we expect to be empty.
     let mut i = 0;