Re-fetch asset via getAsset() on successful PUT/POST
If a POST or PUT request succeeds, re-fetch the asset via getAsset to make sure that the record in assets.assetsByUrl is fresh. Most of the time this will be freshened when the asset list is re-fetched but in some circumstances this will not happen.
As an example: user is a member of two institutions, A and B.
- They start on list of A assets.
- They edit an asset to move it to B.
- On saving they are re-directed back to list of A assets.
Our asset cache is now stale. There are other examples. Many probably don't matter in the long run but we should re-fetch the asset to cover ourselves in all cases.
Closes #86 (closed)