[Bug] Get exception message even though functionsWorkerEnabled is set correctly when starting the function

### Search before asking

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

### Version

`2.10.2.4`
ps: `streamnative/sn-pulsar:2.10.2.4`

### Minimal reproduce step

Try to use the example function:

```bash
bin/pulsar-admin functions create \
--function-config-file examples/example-function-config.yaml \
--jar examples/api-examples.jar
```

### What did you expect to see?

The function successfully created

### What did you see instead?

It returns the message:
```
Pulsar Function Worker is not enabled, probably functionsWorkerEnabled is set to false
```

### Anything else?

The `functionsWorkerEnabled` in `standalone.conf` has been set to true, and this is confirmed in the log when Pulsar starts.

This doesn't look like a configuration issue, what could be the reason for this, is there any more information I can provide?

### Are you willing to submit a PR?

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

Start with the functions-admin create path invoked by bin/pulsar-admin functions create, using examples/example-function-config.yaml and the standalone.conf functionsWorkerEnabled setting as the reproduction inputs. Compare the setting seen at startup with the worker-state check that produces the reported message. Done means the example function is created successfully when functionsWorkerEnabled is true.

Written by the indexing model from the issue text.