rubico/x/memoize

### memoize
```coffeescript
var key any,
cache Mapany>,
funcArgs ...any,
func ...funcArgs=>Promise|any,
maxCacheSize number,
cacheClearer (cache, ...funcArgs)=>Promise<>|key

memoize(func) -> memoized function
memoized.cache -> cache

memoize(func, options {
cacheSize: number,
}) -> memoizedCapped function

memoizedCapped.cache -> cache
```

Memoize (create a cached version of) a function using its first argument as the cache key. If `cacheSize` is provided, it is used to indicate the maximum size of the internal cache. If the number of items in the cache exceeds this number, the cache is cleared. If instead `cacheClearer` is provided, it is called with a reference to the internal cache and any arguments supplied to the memoized function.

Note: Any effects of `func` will not be rerun on cache hit.

```javascript
const identity = value => value

const square = number => number ** 2

const memoizedCapped500Square = memoize(square, { cacheSize: 500 })

console.log(memoizedCapped500Square(3)) // 9
console.log(memoizedCapped500Square.cache) // Map { 3 => 9 }
```

Look at the existing memoize implementation in the codebase to understand the current caching behavior. The task is to add cache size limiting and a custom cache clearer. Start by examining how the cache Map is managed and where eviction logic would fit. Write tests for the new options to verify cache size enforcement and clearer invocation.

由索引模型根據 Issue 內容生成。