Feature Request Allow ScopedRegistries in package.json so user intervention isn't required to resolve dependencies

Issue: When making an asset to release to the public, often developers will make use of Scoped Registries to use dependencies from for example OpenUPM. But there is no way to define these Scoped Registries in the package.json of the asset we release. Thus requiring users to manually add these registries in their Project Settings... defeating the purpose of the package.json file.

Surely this wouldn't be too difficult to implement, and would greatly expand the package system's capabilities.
Simply check for the dependencies within the package.json's scopedRegistries and if they can't be resolved, then check the Project level scopes.

Old complaint thread about it here: https://forum.unity.com/threads/scoped-registry-in-package-json-not-working.868831/

 

Would love to see this functionality too.

I'm trying to export a full project template for the Asset Store (using Unity's official Asset Store Tools). Everything goes well and the manifest and settings are exported, but not the Package Manager settings... which means Custom Scoped Registries are lost.

Which means that even if the manifest lists the correct package, it ends up not being found because the scoped registry is not there.