bug: Configuring fluent-watcher

### Describe the issue

HI Team, I deployed fluent-bit using fluent operator v3.3.0. In case of any configuration change, the changes are not effective unless if we restart the fluent-bit pods manually. Tried using fluent-watcher with the below changes in values.yaml.
# Fluent-watcher
command: ["/fluent-bit/bin/fluent-bit-watcher"]
# custom command line arguments.
args:
- "-c=/fluent-bit/etc/fluent-bit.conf"
- "-watch-path=/fluent-bit/etc

With these chagnes, the configurational changes are not effective unless with a manual restart. Can you please let me know if I am missing anything?

### To Reproduce

Incorporated fluent-watcher with the below changes:
# Fluent-watcher
command: ["/fluent-bit/bin/fluent-bit-watcher"]
# custom command line arguments.
args:
- "-c=/fluent-bit/etc/fluent-bit.conf"
- "-watch-path=/fluent-bit/etc"

The configurational changes should be effective without a manual restart of fluent-bit pods.

### Expected behavior

The configurational changes should be effective without a manual restart of fluent-bit pods with fluent-watcher

### Your Environment

```markdown
- Fluent Operator version: v3.3.0 on a k8s cluster.
```

### How did you install fluent operator?

_No response_

### Additional context

_No response_