Aspire.Host.Docker - resource published as docker-compose service, although PublishAsDockerComposeService not applied.

Having code:
```
var builder = DistributedApplication.CreateBuilder(args);
var kafkaConnectionString = builder.AddConnectionString("kafka");
var compose = builder.AddDockerComposeEnvironment("compose")
var redis = builder.AddRedis("redis", 6379)
var testOrleans= builder.AddOrleans("test-orleans")
.WithClustering(redis)
.WithClusterId("test1")
.WithServiceId("test1");

var silo = builder.AddProject("test")
.WithReference(testOrleans)
.WithReference(redis)
.WithReference(kafkaConnectionString)
.WithReplicas(2)
.WaitFor(redis)
.PublishAsDockerComposeService((conf, service) =>
{
service.Name = "test";
})
```

gives ouput:
```
services:
compose-dashboard:
image: "mcr.microsoft.com/dotnet/nightly/aspire-dashboard:latest"
expose:
- "18888"
- "18889"
networks:
- "aspoire"
restart: "always"
redis:
image: "docker.io/library/redis:8.2"
command:
- "-c"
- "redis-server --requirepass $$REDIS_PASSWORD"
entrypoint:
- "/bin/sh"
environment:
REDIS_PASSWORD: "${REDIS_PASSWORD}"
expose:
- "6379"
networks:
- "aspire"
test:
image: "${TEST_IMAGE}"
...
```

### Expected Behavior

redis should be registered as environment variable, and not as a service, otherwise what is the point of calling PublishAsDockerComposeService.

In case if redis is shipped as standalone service in production environment, it should not be published as service in docker-compose. But should work only on local aspire run/debug. If someone wants to ship redis as part of docker-compose, he should apply PublishAsDockerComposeService method on redis resource.

### .NET Version info

10.0.100

aspire 13.0