…40812)

#### Description
- Fix internal counter for the rate limiter feature
- Added some E2E tests that can be run with a proper API key
- Added new tests to handle this situation

#### Link to tracking issue
Fixes open-telemetry#40811

<!--Describe what testing was performed and which tests were added.-->
#### Testing
##### Manual test

This is the [output
log](https://github.com/user-attachments/files/20802604/output.txt). You
will be able to see how:
1. The exporter tries to send data
2. The rate limit mechanism is enabled
3. Every try to send data will print an error explaining when the rate
limiting started
4. After the duration, the exporter tries to send data again
5. The rate limit feature is enabled again

Configuration used:
```
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: "localhost:4317"
exporters:
  coralogix:
    domain: "eu2.coralogix.com"
    private_key: "${env:CORALOGIX_PRIVATE_KEY_LOW_QUOTA}"
    application_name: "MyBusinessEnvironment"
    subsystem_name: "MyBusinessSystem"

    rate_limiter:
      enabled: true
      threshold: 5
      duration: 10s

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [coralogix]
```

##### E2E test
Log output
[e2e_output.log](https://github.com/user-attachments/files/20802689/e2e_output.log)

Signed-off-by: Israel Blancas <[email protected]>