Trying to load a fork of a baseline after loading the original fails with error MetacelloConflictingProjectError #557
Description
If you load a metacello script in a pharo image (but assume this applies to all smalltalks) and then decide to fork that project, and you want to reload the fork - metacello insists on loading the original repository because the MetacelloProjectRepository>>registrationFor: aMetacelloProjectRegistration ifPresent: presentBlock ifAbsent: absentBlock
uses only the basline name to distinguish what to load
e.g. self baselineRegistry at: spec className ifPresent: [ :existing | ^ presentBlock value: existing ]
This means you can't easily load a different variant of the baseline. The key to the registroy should be name+repo name.