Add Deployment Keys information in the licensing section

[DinkoK]

No description provided.

[Copilot]

Pull request overview

This PR updates the CI/CD licensing documentation to introduce deployment keys as the recommended credential for build pipelines, and adjusts the activation setup steps accordingly.

Changes:

• Replaces the CI/CD licensing intro to focus on deployment keys rather than general license keys.
• Adds step-by-step instructions for creating an application and generating a deployment key in the Telerik account.
• Updates the CI/CD activation guidance to use the generated key via TELERIK_LICENSE (or a telerik-license.txt file for Azure secure files).

Suppressed comments (2)

installation/licensing/installing-license-to-ci-services.md:19

• The new deployment-keys section repeats the same statement twice, and the admonition syntax uses > important / > tip with a space, which appears inconsistent with the docs’ established >important / >tip format (for example, getting-started/first-steps-nuget.md:50-61). Also, the tip still refers to a "provided license key" even though this section introduces deployment keys.

Deployment keys are a dedicated type of license key for build pipelines. They’re tied to a specific application and the set of products that the application uses. Deployment keys cannot be used for application development.

> important Deployment keys cannot be used for application development.

> tip When working with CI/CD platforms, always add the `Telerik.Licensing` NuGet package as a project dependency. This package activates Telerik UI for WPF at build time by using the provided license key.

installation/licensing/installing-license-to-ci-services.md:35

• The environment variable name is formatted in bold here, but elsewhere in this doc it’s consistently shown as inline code (for example, TELERIK_LICENSE in the GitHub Actions and Azure Pipelines sections). Using code formatting improves readability and avoids inconsistent styling.

1. [Create an environment variable](#creating-an-environment-variable) named **TELERIK_LICENSE** and set it to the obtained key value. 

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.