Make rate limit behavior configurable for dropping or queuing

[matux]

Description of the change

This is the final PR for 122305 following #276.

This PR introduces the ability to configure some behavior when dealing with rate limiting. Users can now specify whether they'd like to drop occurrences (and their API requests) that fall under rate limit, or keep them in the queue to be sent in the next window of time.

The default behavior is to drop the rate limited occurrence.

If there are persisted occurrences at the moment the application starts, and behavior is configured to drop occurrences, all the persisted occurrences will be removed iff the first attempt at sending a persisted occurrence is rate limited.

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Maintenance
• New release

Related issues

• Fixes 122305
• Fixes Rate limiting isn't handled correctly which results into more requests to be sent #255.

Checklists

Development

• Lint rules pass locally
• The code changed/added as part of this pull request has been covered with tests
• All tests related to the changed code pass in development

Code review

• This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
• "Ready for review" label attached to the PR and reviewers assigned
• Issue from task tracker has a link to this pull request
• Changes have been reviewed by at least one other engineer

[ijsnow]

🔢