FAIR package metadata being overwritten by generated data

[chuckadams]

When AC imports a plugin or theme through the legacy import endpoint, it generates package metadata for it on the fly and gives it a web DID, but that package overwrites any existing package that may have been imported already from its proper FAIR metadata. This would be solved by the simple optimization of not clobbering existing plugins/themes if the same slug and version already exists. If the version is updated though, there's not a lot that can be done except to wait for the package metadata to come in on the package import endpoint (see issue #359) and connect the package to the existing legacy metadata.

[chuckadams]

this is breaking the ability to demo FAIR functionality in things like AE, so I'm going to make a quick fix for this ASAP, then work on a longer-term solution (which while we're at it can address slug collision between plugins and themes. right now we avoid it by just not bothering with packages for themes)

[chuckadams]

huh, auto-creating packages on import is one of those things I keep thinking we're doing, but when I look into it, is still not happening. The non-legacy packages seem fine, as this exhaustive test on production shows:

$ php artisan tinker
> use App\Models\Package; Package::firstWhere('slug', 'git-updater')->did;
= "did:plc:afjf7gsjzsqmgc7dlhb553mv"