Fix the tracking path of npm metadata

[sswguo]

Fix for MMENG-2881, indy tracks the npm metadata with suffix package.json, which is wrong. I checked and found it just happens when client requests the metadata from group repo, the PR is to keep the origin path in EventMetadata and set it during tracking.

[ruhan1]

LGTM

[ligangty]

Seems only the GET method is covered. Should we also check the HEAD and PUT methods?
And another little nitpick: seems all the REST doc description(@apioperation) is confused, maybe we should consider to give some better docs.

[sswguo]

Seems only the GET method is covered. Should we also check the HEAD and PUT methods?

We don't track HEAD in folo, so it's ok to ignore the HEAD, for PUT, we can ask @pkocandr to confirm if this is the same case with GET.

And another little nitpick: seems all the REST doc description(@apioperation) is confused, maybe we should consider to give some better docs.

Yeah, seem so. : ) Will tweak them in another PR.

[sswguo]

Checked the folo records of the build mentioned in the jira, there is no such issue for PUT request, I will merge this and do test on devel. thanks.