Update package.json to discard tag_prefix to make npm binary mirroring work

[tomduncalf]

What, How & Why?

A user reported in #4667 that they cannot install Realm using npm "binary mirroring", which allows it to work in an environment with no internet connection and instead, an internal artefact server – I guess quite a common set up in finance, etc. This happened since v10, it used to work in v6.

They did some research and suggested that this change would fix the issue. They tested this branch and it did indeed fix the issue, but I have to confess I don't really understand the consequences of the change so would welcome any thoughts!

☑️ ToDos

• 📝 Changelog entry
• 📝 Compatibility label is updated or copied from previous entry
• 🚦 Tests
• 🔀 Executed flexible sync tests locally if modifying flexible sync
• 📦 Updated internal package version in consuming package.jsons (if updating internal packages)
• 📱 Check the React Native/other sample apps work if necessary
• 📝 Public documentation PR created or is not necessary
• 💥 Breaking label has been applied or is not necessary

If this PR adds or changes public API's:

• typescript definitions file is updated
• jsdoc files updated
• Chrome debug API is updated if API is available on React Native

[kneth]

LGTM. I wonder if the experience will be better if we migrate to Github releases instead of using S3?