fix(ci): add telemetry profile to dev grafana service (#16777)

[YAMRAJ13y]

Proposed changes

The dev stack in opencti-platform/opencti-dev could not be started with the documented command:

$ docker compose up -d
service "opencti-dev-telemetry-grafana" depends on undefined service "opencti-dev-telemetry-prometheus": invalid compose project

grafana had no profiles while depends_on the telemetry-profiled prometheus, making the default project invalid. This change adds profiles: [telemetry] to grafana, consistent with the other telemetry services (prometheus, otlp, jaeger, pyroscope).

Related issues

Closes #16777

How to test

From opencti-platform/opencti-dev:

# Before: both fail with 'invalid compose project'
# After:
docker compose config >/dev/null && echo OK          # default project is valid
docker compose config --services                      # core services, no grafana
docker compose --profile telemetry config --services  # includes opencti-dev-telemetry-grafana

Verified locally: the default project is valid, grafana is excluded by default and included with --profile telemetry, and docker compose up -d brings up the core dependencies.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[YAMRAJ13y]

The failing Backend / Integration tests run looks like an unrelated CI infrastructure flake rather than something caused by this change. The job log ends with the platform failing its startup dependency check against Elasticsearch:

connect ECONNREFUSED <es-host>:9200
CONFIGURATION_ERROR: Search engine seems down
[OPENCTI] System dependencies check failed

This PR only adds profiles: [telemetry] to the grafana service in the dev docker-compose.yml, which is not used by the backend integration test stack, so it can't affect search-engine connectivity. Could a maintainer re-run the job when convenient? Happy to rebase if you'd prefer.