Reduce the number of rest calls while doing Rename Operation

[syeleti-msft]

✅ What

Currently we invalidate the cache item of destination after the rename operation completes, this can be identified in the final call of the following flow:
Rename on FNS:
API calls: There are 5 REST api calls assosiated with this operation.

1. GetAttr(src)---------list call (filesystem call)
2. GetAttr(dst)---------list call (filesystem call)
3. copyblob(src->dst)----------(rename function)
4. deleteblob(src)--------------(rename function)
5. GetAttr(dst)---------list call (filesystem call)

Rename on HNS:
API Calls: There are 4 REST api calls assosiated with this operation.

1. GetAttr(Dst)
2. GetAttr(Src)
3. RenamePathFile
4. GetAttr(dst)

goal is to serve the last call for FNS&HNS in the above REST calls from the attribute cache.

🤔 Why

The idea is to simply copy Src Attributes to the destination when the rename is success.
The only thing that modified in the destination was the last modified time, it will be modified according to the response of REST call for rename in AzStorage Component.

👩‍🔬 How to validate if applicable

Do rename operation with "mv" and see that the Final GetAttr on Dst after rename is success will be served from the cache.