feat: delete expired background queue tasks

[levibostian]

Complete each step to get your pull request merged in. Learn more about the workflow this project uses.

• [x] Assign members of your team to review the pull request.
• [x] Wait for pull request status checks to complete. If there are problems, fix them until you see that all status checks are passing.
• [ ] Wait until the pull request has been reviewed and approved by a teammate
• [ ] After pull request is approved, and you determine it's ready add the label "Ready to merge" to the pull request and it will automatically be merged.

[codecov[bot]]

Codecov Report

Merging #108 (95031d7) into develop (72f9753) will increase coverage by 2.20%. The diff coverage is 86.51%.

@@              Coverage Diff              @@
##             develop     #108      +/-   ##
=============================================
+ Coverage      64.72%   66.93%   +2.20%     
- Complexity       129      138       +9     
=============================================
  Files             63       64       +1     
  Lines           1222     1255      +33     
  Branches         132      136       +4     
=============================================
+ Hits             791      840      +49     
+ Misses           366      356      -10     
+ Partials          65       59       -6     

Impacted Files	Coverage Δ
...ava/io/customer/base/extenstions/DateExtensions.kt	90.90% <50.00%> (-9.10%)	:arrow_down:
...ain/java/io/customer/sdk/di/CustomerIOComponent.kt	61.01% <50.00%> (+3.12%)	:arrow_up:
...n/java/io/customer/sdk/util/DispatchersProvider.kt	66.66% <66.66%> (ø)
...rc/main/java/io/customer/sdk/queue/QueueStorage.kt	88.33% <86.53%> (+2.61%)	:arrow_up:
sdk/src/main/java/io/customer/sdk/CustomerIO.kt	56.73% <100.00%> (+3.60%)	:arrow_up:
.../src/main/java/io/customer/sdk/CustomerIOConfig.kt	100.00% <100.00%> (+6.25%)	:arrow_up:
sdk/src/main/java/io/customer/sdk/di/DiGraph.kt	100.00% <100.00%> (ø)
sdk/src/main/java/io/customer/sdk/queue/Queue.kt	80.68% <100.00%> (+0.44%)	:arrow_up:
...va/io/customer/sdk/repository/CleanupRepository.kt	100.00% <100.00%> (ø)
sdk/src/main/java/io/customer/sdk/util/Seconds.kt	90.90% <100.00%> (+10.90%)	:arrow_up:
... and 6 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 72f9753...95031d7. Read the comment docs.

[ami-oss-ci]

Pull request title looks good 👍!

If this pull request gets merged, it will cause a new release of the software. Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.1.0. This pull request is not a breaking change.

All merged pull requests will eventually get deployed. But some types of pull requests will trigger a deployment (such as features and bug fixes) while some pull requests will wait to get deployed until a later time.

To merge this pull request, add the label Ready to merge to this pull request and I'll merge it for you.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...

This project uses a special format for pull requests titles. Don't worry, it's easy! This pull request title should be in this format: ``` : short description of change being made ``` **If your pull request [introduces breaking changes](https://web.archive.org/web/20220725195319/https://nordicapis.com/what-are-breaking-changes-and-how-do-you-avoid-them/)** to the code, use this format: ``` !: short description of breaking change ``` where `` is one of the following: - `feat:` - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project. - `fix:` - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project. - `docs:` - This pull request is making documentation changes, only. - `refactor:` - A change was made that doesn't fix a bug or add a feature. - `test:` - Adds missing tests or fixes broken tests. - `style:` - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc) - `perf:` - Changes improve performance of the code. - `build:` - Changes to the build system (maven, npm, gulp, etc) - `ci:` - Changes to the CI build system (Travis, GitHub Actions, Circle, etc) - `chore:` - Other changes to project that don't modify source code or test files. - `revert:` - Reverts a previous commit that was made. ### Examples: ``` feat: edit profile photo refactor!: remove deprecated v1 endpoints build: update npm dependencies style: run formatter ``` Need more examples? Want to learn more about this format? [Check out the official docs](https://www.conventionalcommits.org/). **Note:** If your pull request does multiple things such as adding a feature _and_ makes changes to the CI server _and_ fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.

[github-actions[bot]]

Build available to test Version: levi-delete-expired-queue-SNAPSHOT Repository: https://s01.oss.sonatype.org/content/repositories/snapshots/

[ami-ci]

:tada: This PR is included in version 2.1.0-alpha.1 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

[ami-ci]

:tada: This PR is included in version 2.1.0-beta.1 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

[ami-ci]

:tada: This PR is included in version 2.1.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: