feat(requests-result): 🔥 Add ttl to updateRequestsCache

[johnfewell]

Add a ttl parameter to the updateRequestsCache function, allowing users to set an expiration time for each cache record when updating multiple keys. If a ttl value isn't provided, the cache record doesn't expire.

✅ Closes: 471

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngneat/elf/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Currently, the updateRequestsCache function updates the cache state for a given set of keys to a specified value. However, it doesn't allow for setting an expiration time for these cache records.

Issue Number: 471

What is the new behavior?

With this update, users can now set a ttl parameter when calling the updateRequestsCache function. This parameter allows for setting an expiration time for each cache record. After the set time has elapsed, the cache record for the key will revert to 'none'. If a ttl value isn't provided, the cache record will persist and won't automatically expire.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

The introduction of the ttl parameter enhances the flexibility and control users have over cache management in their applications. This feature can be particularly useful in scenarios where the validity of data might change over time.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.