Enable path-only changes to metadata to trigger asset change

[waxlamp]

The logic for PUT on asset metadata includes a check to see if the asset is "different" enough to warrant an actual change. This works in part by stripping the supplied metadata of all computed fields, of which path is one, and then comparing what remains. This had the effect of barring any "move" type operations (by changing just the path value of a metadata and performing a PUT), as changes to the path did not "count" towards being different enough. The workaround was to also change a non-computed metadata field; this made the asset different enough to trigger a change, which included the changed path.

The fix is to teach the "is different" function about path-only changes.

Thanks to @AlmightyYakob for his help in figuring this out.

TODO:

• add a test (@AlmightyYakob)

Closes #1682.

[jjnesbitt]

I've confirmed that the test included in 65cf41f fails on master, but succeeds on this branch.

[jjnesbitt]

The tests seem to be failing due to some underlying issue which is also affecting master, and it not a result of this PR (evidenced via https://github.com/dandi/dandi-archive/actions/runs/6319690526).

[mvandenburgh]

The tests seem to be failing due to some underlying issue which is also affecting master, and it not a result of this PR (evidenced via dandi/dandi-archive/actions/runs/6319690526).

#1691 should make CI green again.

[yarikoptic]

Let's rebase to see tests pass (or not)?

[satra]

let's also get this in a release so that @slaytonmarx can fix some of those files.

[dandibot]

🚀 PR was released in v0.3.55 🚀