Update kedro-telemetry to use the CI environment variable to indicate that data comes from a CI environment

[noklam]

Description

Use the CI environment variable to differentiate runs between a CI/CD environment and a real kedro project run for data collection.

kedro-org/kedro#1640 (comment)

I think it would be good to take this opportunity to distinguish CI runs in telemetry. Maybe can read an environment variable; most CI systems (GitHub Actions, CircleCI, Travis CI, etc.) follow the convention of setting CI=true, so I would recommend detecting presence of the environment variable, solving the telemetry prompt automatically, and recording commands as belonging to a CI run--and ideally not requiring any additional configuration or hacks to avoid this telemetry prompt.

Whoever pick up this ticket should double check if CI is a standard convention we can use. Alternatively, we can refer to how Dagester do it:
https://github.com/dagster-io/dagster/blob/e31e577b8841e0ff54745e206d621d9bf934a063/python_modules/dagster/dagster/_core/telemetry.py#L92

[datajoely]

I still think this should be CLI command as well

[noklam]

It's here

• Add an option for kedro new and kedro run to skip telemetry (e.g. for CI/CD environment) kedro#2867

Parent issue:

• Improve running kedro as part of an automated workflow (CI/CD) kedro#1640

[astrojuanlu]

This is about reporting that Kedro is being run from a CI environment.

[astrojuanlu]

Example: How Dagster does it: https://github.com/dagster-io/dagster/blob/e31e577b8841e0ff54745e206d621d9bf934a063/python_modules/dagster/dagster/_core/telemetry.py#L92-L101