Regression when matching to database as uninstrumented peer

[JamesNK]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

This call to a database no longer matches the database resource:

I think it could be caused by the address matching to the database and the database container. Possibly introduced by #10411 (or the earlier PR which updated matching to use additional values)

Edit: reverted to before and after #10411 and it is definitely the cause

Expected Behavior

From viewing a trace of visiting the online store in TestShop.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version info

No response

Anything else?

No response

[JamesNK]

cc @davidfowl

[JamesNK]

It also doesn't match replicas when a request is made to a replica but the server span from the replica has finished yet:

Previously one of the replicas was chosen.

[davidfowl]

Its possible that we need more complex logic here but for 9.4 we will just remove this logic (revert the change). Lets put this logic back

aspire/src/Aspire.Dashboard/Model/ResourceOutgoingPeerResolver.cs

Lines 195 to 205 in b154569

	if (foundResource is null)
	{
	foundResource = resource;
	}
	else if (!string.Equals(foundResource.Name, resource.Name, StringComparisons.ResourceName))
	{
	// Multiple different resources match - return false immediately
	name = null;
	resourceMatch = null;
	return false;
	}

to first one wins and revert the tests that were added in https://github.com/dotnet/aspire/pull/10411.diff as well