feat: getOrSet

[corradodellorusso]

Please check if the PR fulfills these requirements

• Followed the Contributing guidelines.
• Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This pull request introduces a new getOrSet method to the Cacheable class, refactors the wrap function to leverage this new method, and adds corresponding tests to ensure functionality. The changes aim to improve cache management by simplifying code and preventing cache stampedes.

New Features:

• Added a getOrSet method to the Cacheable class, which retrieves a cached value or computes and caches it if not present. This method includes support for TTL and error caching. (packages/cacheable/src/index.ts)

Refactoring:

• Refactored the wrap function to delegate caching logic to the new getOrSet method, simplifying the implementation. (packages/cacheable/src/wrap.ts)

Type and Import Updates:

• Introduced a new GetOrSetOptions type to encapsulate options for the getOrSet method. (packages/cacheable/src/index.ts)
• Updated imports to include coalesceAsync in index.ts and removed it from wrap.ts as it is now used exclusively in getOrSet. (packages/cacheable/src/index.ts, packages/cacheable/src/wrap.ts) [1] [2]

Testing Enhancements:

• Added tests for the getOrSet method to verify proper caching behavior and prevention of cache stampedes. (packages/cacheable/test/index.test.ts)
• Minor cleanup in wrap.test.ts by removing unused imports. (packages/cacheable/test/wrap.test.ts)

[jaredwray]

@corradodellorusso - thanks and will do a review tomorrow.

[jaredwray]

I noticed you replaced the wrap function with your getOrSet. Should we do that as I do plan long term to have wrap be in its own module that enables cache-manager and cacheable.

done