[71,72] Track item moving between vaults and requests rate limits

Ok, I'm finally back and have some time.

Do you run into rate-limits with op item get after op item list when the cache is enabled? Although op item get displays more data than op item ls does, op item ls currently already fetches this data, so it should already be available in the cache.

Frankly speaking, I have doubts --cache works at all (or I use it in a wrong way somehow, or it works only under some specific conditions).

Things I did:
- Run op item list --cache --session my-session-key.
- Found a single item in the result data set with my-item-id.
- Updated that item via the web client (updated the title).
- Run op item get my-item-id --session my-session-key.
- As a result, got an updated item (not the one that should have been cached).

So, seems like cache does not work or I'm using it in the wrong way.

And one more question: let's imagine cache does work, so is there a way to limit the cache time? Based on the documentation, it caches data for 24 hours (which is definitely not cool). Is there a way to set a specific duration to cache the data for, e.g. an hour or so? If I run op item list --cache once more, will it update the cached data right away, even if the 24 hours have not passed yet?