Added support for deploying multiple fluentbit collector replicas

[solidDoWant]

What this PR does / why we need it:

Fluent bit collectors can only be deployed with one replica. Deploying multiple requires deploying separate collector resources and handling iterative naming (e.g. collector-1, collector-2) manually. This PR adds the replica field, matching the fluentd collector logic.

Which issue(s) this PR fixes:

N/A

Does this PR introduced a user-facing change?

Added the ability to deploy multiple fluentbit collector replicas.

Additional documentation, usage docs, etc.:

N/A

[wenchajun]

I think this is a good modification, but here replicas should be given a default value in the helm package and yaml file.

[solidDoWant]

@wenchajun is this sufficient? This now matches the same logic that is used for Fluentd STSs. There are not currently any kind: Collector manifests in the repo.

[wenchajun]

@wenchajun is this sufficient? This now matches the same logic that is used for Fluentd STSs. There are not currently any kind: Collector manifests in the repo.

config like this https://github.com/fluent/fluent-operator/blob/master/charts/fluent-operator/values.yaml#L450. You can also write it down and comment it out. But I think it has to be reflected in chat&&yaml.

[wenchajun]

@wenchajun is this sufficient? This now matches the same logic that is used for Fluentd STSs. There are not currently any kind: Collector manifests in the repo.

That is fine，too