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

Hi kovpack,
thank you for writing such a detailed response! This is really helpful for us!

I can https://1password.community/discussion/comment/629495/#Comment_629495e . Are you able to see it now too?

In a perfect world I'd not expect such a behavior.

I'll start here, with the underlying issue (moves that change the ID). I'll start discussing and coordinating this internally. If/when we're going to change this it will need to be changed across all the apps (luckily https://blog.1password.com/1password-8-the-story-so-far/ 😀).

Even when we would make that change across all the apps, old client versions will still do a create+delete under the hood, so you'd either need to make sure everyone updates if/when that update would become available or continue to have the workaround available for items moved in older versions.

For your work-around:
- Does op item get have the data available that you require?
- What are the names for the data in op item get that you need that are not in op item list?
- 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.
- Is your problem only with hitting rate-limits when executing a command for each item or are there any other problems with running multiple commands?

I'm inquiring internally about the rate-limits. Unfortunately, I believe they are not static (i.e. what I share today may not hold later) and there is currently no way to fetch your current and open rate-limit. There are some plans around improving the rate-limits in general and I have attached this conversation as an up-vote on planning that work.

Thanks again for writing in with such a detailed reply, this is really helpful for us!