fix: 🐛 fix destroy and cacheRequest lock

[self-transition]

1. Cause of requestsCache didn't lock listWatch onResponse callback, In some cases, multiple connections may have been established and the older connections are not managed by the global store.
2. In previous fix _isDestroyed has too great a reach, The flag should only affect the get method

Before
We can see that two connections were established when the same resource was initialized, and that the connection established first was taken out of the management

After

BTW, there is an another case left: if the request onResponse callback is timeout and didn't trigger error, the cache request lock will not be removed