[fix][broker] Fix getMessageById throws 500

[nodece]

Motivation

When using bin/pulsar-admin topics get-message-by-id public/default/my-topic-1 -e 0 -l 1024 with a non-existent ledger, I expect to throw the 400 error instead of 500.

CLI log:

$ bin/pulsar-admin topics get-message-by-id public/default/my-topic-1 -e 0 -l 1024

 --- An unexpected error occurred in the server ---

Message: Message not found, the ledgerId does not belong to this topic or has been deleted

Stacktrace:

org.apache.bookkeeper.mledger.ManagedLedgerException$LedgerNotExistException: Message not found, the ledgerId does not belong to this topic or has been deleted


Reason: 
 --- An unexpected error occurred in the server ---

Message: Message not found, the ledgerId does not belong to this topic or has been deleted

Stacktrace:

org.apache.bookkeeper.mledger.ManagedLedgerException$LedgerNotExistException: Message not found, the ledgerId does not belong to this topic or has been deleted

Broker log:

2024-01-18T18:03:46,824+0800 [pulsar-web-47-14] INFO  org.eclipse.jetty.server.RequestLog - 127.0.0.1 - - [18/1月/2024:18:03:46 +0800] "GET /admin/v2/persistent/public/default/my-topic-1/ledger/1024/entry/0 HTTP/1.1" 500 340 "-" "Pulsar-Java-v3.2.0" 29

Modifications

• In the internalGetMessageById, when readEntryFailed returns LedgerNotExitException, convert this exception to 400 error.
• When the admin receives the 400 error, skip handle recovery.

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

[dao-jun]

lgtm

[nodece]

/pulsarbot rerun-failure-checks