[Bug] Bookie instanceId verification failed

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Read release policy

- [X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

### Version

image: 3.0.4
k8s deploy

### Minimal reproduce step

First, the cluster bookies prompts that it cannot get **instance_id** and asks me to use **bin-bookkeeper shell metaformat** to initialize. Then restarting bookies reports this error. I take the **instanceId 237fe99b-9a46-4697-bff1-4739d68a9175 is not matching with 52088892-8876-4c1c-b6fa-cf00e487d985** prompt 237fe99b-9a46-4697-bff1-4739d68a9175 to the bookies host to modify the VERSION file. Then restarting it still has the same error, but this time it no longer prompts the instanceId to be modified.

### What did you expect to see?

I expect it to start normally

### What did you see instead?

org.apache.bookkeeper.bookie.BookieException$InvalidCookieException:

### Anything else?

Solution

### Are you willing to submit a PR?

- [X] I'm willing to submit a PR!

Start with the BookieException$InvalidCookieException path and the bin-bookkeeper shell metaformat flow described in the report. Inspect how the VERSION file and instance_id are read and compared during bookie startup. Done means reproducing the mismatch on Pulsar 3.0.4 and identifying a verified correction that lets the bookie restart normally.

Written by the indexing model from the issue text.