[Bug]: service-name configuration property is ignored

DAB ignores the `runtime.telemetry.open-telemetry.service-name` configuration value and always uses the value from the first startup or a hardcoded default.

## Expected

Changing `service-name` in `dab-config.json` and restarting DAB should update the `service.name` resource attribute in all exported OTEL data.

```json
{
"runtime": {
"telemetry": {
"open-telemetry": {
"enabled": true,
"endpoint": "http://localhost:4318",
"service-name": "dab-otel-test-http",
"exporter-protocol": "httpprotobuf"
}
}
}
}
```

Expected OTEL resource: `service.name: Str(dab-otel-test-http)`

## Actual

Three separate DAB processes (confirmed by 3 unique `service.instance.id` values) were started with different `service-name` values: `dab-otel-test`, `dab-otel-test-http`, and `dab-otel-DISABLED`. All three processes exported data with:

```
-> service.name: Str(dab-otel-test)
```

The `service-name` property appears to be read only once or is overridden by the SDK default/environment.

Commencez par suivre le paramètre runtime.telemetry.open-telemetry.service-name depuis dab-config.json jusqu’à la configuration des ressources OpenTelemetry. Reproduisez le problème en redémarrant DAB avec différentes valeurs de service-name et en inspectant les attributs de ressources exportés. Le travail est terminé lorsque chaque processus exporte service.name correspondant à sa valeur configurée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.