Named services cyclic dependency

[MitchRazga]

Hi,
I've been playing around with the new named services feature and thought it could useful for resolving relative URIs into absolute URIs.

Before named services this would have been difficult to achieve since having a Uri depend on another Uri understandably causes a cyclic dependency.
However, now that a specific registration can be injected by name this seems like this should be possible but still causes the cyclic dependency. Is this by design?

I've recreated a basic repro. Please see attached.
JabNamedServices.zip

[ServiceProvider]
[Singleton<Uri>(Factory = "BaseUriFactory", Name = "Base")]
[Singleton<Uri>(Factory = "FullUriFactory", Name = "Full")]
internal partial class Services
{
	static Uri BaseUriFactory() => new(@"C:\");

	static Uri FullUriFactory([FromNamedServices("Base")] Uri baseUri)
	{
		Uri relativeUri = new(@"Test\", UriKind.Relative);
		return new(baseUri, relativeUri);
	}
}

As a workaround I've found I can just inject IServiceProvider for a runtime resolution which is still pretty useful.

static Uri FullUriFactory(IServiceProvider serviceProvider)
{
	Uri baseUri = serviceProvider.GetRequiredKeyedService<Uri>("Base");
	Uri relativeUri = new(@"Test\", UriKind.Relative);
	return new(baseUri, relativeUri);
}