Add Endpoint.BrokerRole for CritterWatch endpoint display (#2601)

[jeremydmiller]

Summary

Closes #2601.

Adds a new virtual string BrokerRole { get; protected set; } on the base Endpoint class with default "endpoint". Each transport-specific subclass sets it in its own ctor; NatsEndpoint overrides because Core NATS vs JetStream is a runtime choice.

The companion DisplayName property described in the issue was deferred — see the audit below; EndpointName already covers most of that need.

BrokerRole values per endpoint

Endpoint	BrokerRole
RabbitMqQueue	queue
RabbitMqExchange, RabbitMqRouting	exchange
RabbitMqTopicEndpoint	topic
AzureServiceBusQueue	queue
AzureServiceBusTopic	topic
AzureServiceBusSubscription	subscription
AmazonSqsQueue	queue
AmazonSnsTopic	topic
KafkaTopic	topic
PulsarEndpoint	topic
PubsubEndpoint	pubsub (per @jeremydmiller)
MqttTopic	topic
RedisStreamEndpoint	stream
NatsEndpoint	subject (Core NATS) / stream (JetStream) — runtime override
SqlServerQueue, PostgresqlQueue, TenantedPostgresqlQueue, SqliteQueue, OracleQueue, MySqlQueue	queue
DatabaseControlEndpoint	queue
ExternalMessageTable	table
LocalQueue	queue
SharedMemoryTopic	topic
SharedMemorySubscription	subscription
StubEndpoint	stub
TcpEndpoint	socket (per @jeremydmiller)
HttpEndpoint	route (per @jeremydmiller)
GrpcEndpoint	grpc (per @jeremydmiller)
SignalRTransport, SignalRClientEndpoint	hub (per @jeremydmiller)

Endpoint base default is "endpoint" for any custom subclass that forgets to override.

Tests

• CoreTests/Configuration/broker_role_tests.cs — base default + LocalQueue, StubEndpoint, TcpEndpoint, SharedMemoryTopic, SharedMemorySubscription.
• A broker_role_tests.cs added to every transport / persistence test assembly with a one-line check per concrete endpoint type, so any future endpoint addition that forgets to set BrokerRole fails at test time.
• NATS test specifically covers both subject and stream to exercise the runtime override.

All broker_role_tests pass across 19 test assemblies. Full CoreTests suite (1369/1369) passes — no regression.

EndpointName audit (per Q2 in the design discussion)

Endpoint's base ctor sets EndpointName = uri.ToString() and most subclasses override it to a friendly value. The following concrete subclasses currently fall back to the URI string and may want a friendlier EndpointName for CritterWatch (none are touched in this PR — flagged for follow-up decision):

Endpoint	Falls back to	Suggested
SharedMemoryTopic	memory://topicName	topicName
SharedMemorySubscription	memory://topic/sub	Name (subscription)
HttpEndpoint	full HTTP URI	route template (no obvious constructor source)
GrpcEndpoint	grpc://host:port	\"$host:$port\"
SignalRClientEndpoint	signalr://host:port/hub	hub path
PulsarEndpoint	persistent://tenant/ns/topic	TopicName
TenantedPostgresqlQueue	postgresql://q/dbname	\"$queue@$dbname\"
DatabaseControlEndpoint	db-control://nodeId	\"Control-{NodeId}\"
CosmosDbControlEndpoint	cosmosdb-control://nodeId	same
ExternalMessageTable	external-db://schema.table	TableName.QualifiedName (already friendly)
TcpEndpoint	tcp://host:port (set explicitly to URI)	\"$host:$port\"

Test plan

• dotnet build wolverine.slnx — full solution clean, 0 errors.
• dotnet test src/Testing/CoreTests --framework net9.0 — 1369/1369 pass.
• broker_role_tests pass across 19 transport / persistence test assemblies (RabbitMQ, ASB, SQS, SNS, Kafka, Pulsar, NATS, Pub/Sub, MQTT, Redis, SignalR, SqlServer, Postgresql, Sqlite, Oracle, MySql, Wolverine.Http, Wolverine.Grpc, CoreTests).

🤖 Generated with Claude Code