[chore]: Mention the possibility of having multiple instances of loadbalancingexporter (open-telemetry#35489)

Adding explicit statement about using multiple instances of
`loadbalancingexporter` can help clarify deployment architecture.

Reference:
open-telemetry#22801

**Description:** <Describe what has changed.>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->

**Link to tracking Issue:** <Issue number if applicable>

**Testing:** <Describe what testing was performed and which tests were
added.>

**Documentation:** <Describe the documentation added.>

---------

Co-authored-by: Juraci Paixão Kröhling <[email protected]>
Co-authored-by: Juraci Paixão Kröhling <[email protected]>

Author: 2 people

exporter/loadbalancingexporter/README.md

@@ -78,6 +78,8 @@ The `loadbalancingexporter` will, irrespective of the chosen resolver (`static`,
 
 Unfortunately, data loss is still possible if all of the exporter's targets remains unavailable once redelivery is exhausted. Due consideration needs to be given to the exporter queue and retry configuration when running in a highly elastic environment.
 
+To avoid a single point of failure, requests can be distributed among multiple Collector instances configured with the `loadbalancingexporter`. The consistent hashing mechanism will ensure a deterministic result between instances sharing the same configuration and resolve an exact list of backend endpoints.
+
 ## Configuration
 
 Refer to [config.yaml](./testdata/config.yaml) for detailed examples on using the exporter.