'GitHub Packages' based npm proxy repos causes the long hashed tgz filename/path generation.

When we set up a nexus proxy repository to point to remote repo as https://npm.pkg.github.com then the tgz package names in the nexus UI seems to have a very large hashed tgz binary asset path as shown in the Nexus_UI_Request.png Notice the Asset Path in the screenshot. 

Although when the NPM client downloads the packages using npm pack (or npm install) command then the package is downloaded without any issue. The NPM client can resolve the tarball name correct filename / path (like "someuser-delete_repo-1.0.0.tgz") while storing it locally:

Example:

# npm pack @someuser/delete_repo@1.0.0 -ddd --registry=http://nexus.example.com:8081/repository/npm-package-proxy/
.
.
npm info using npm@6.14.5
npm info using node@v12.18.1
.
.
npm sill tarball no local data for @someuser/delete_repo@1.0.0. Extracting by manifest.
npm http fetch GET 200 http://nexus.example.com:8081/repository/npm-package-proxy/@jaysensharma/delete_repo/-/350f1e0f881b23b379396aa20ddecdd9bee11895ec8163282c171d07ad99ed7e 6ms 
npm sill extract @jaysensharma/delete_repo@1.0.0 extracted to /var/folders/l2/rdmwjccj3kvflbx5bsxkp6sc0000gn/T/npm-19351-ff30da1a/tmp/unpacking-c1393b49/someuser-delete_repo-1.0.0.tgz (12ms)

 Current behaviour:

• Nexus UI shows a very long hash based file name (Path) for the NPM archive (instead of showing correct tgz file)
• Downloading asset directly from Nexus UI or using some other non npm based clients like (curl / UI) downloads the same long hashed file instead of the correct tgz filename.

Expected behaviour:

• Nexus UI should show the correct npm tgz filename in the Nexus Browse UI.