atproto package references are scoped to `https://npmx.dev`, should be unscoped

[uwx]

Records like dev.npmx.feed.like have a subjectRef like https://npmx.dev/package/<packagePath>. This places a soft dependency on the main npmx.dev AppView, which is not very AT. I suggest changing it to be something like npm:<packagePath> which Constellation will still parse as a URI and resolve backlinks to. Alternatively it could be scoped to the owning registry, which is the defacto owner of the package being referenced, like https://registry.npmjs.org/<packageName>. Then it could have a different hostname if npmx ever gets support for third party registries.

[fatfingers23]

Thank you for the issue! I think in the end we may end up moving to link to the registry instead. The deciding factors that went into using a npmx.dev URL was:

• We needed a URL for constellation and not every package is going to end up with an atproto record so needed a way to tie to it
• I had fears of doing something like npm:<packagePath>. Felt a bit odd to me for making a scheme for just that.
• Landed on the npmx url since this is a lexicon for npmx and thinking we would want to show that it's a like from npmx. Our atproto integration can probably be thought more of "We use atproto to power some of our social features" Instead of us being a full fledge atproto app. So we've been trying to find solutions that meet in the middle.

[uwx]

Yeah I think scoping to the registry is the closest thing to what you want here. Avoids having an arbitrary protocol and points to where the package is owned