docs(Common): Add TelerikLicensingStrict to license warnings as errors (#3015)

* docs(Common): Add TelerikLicensingStrict to license warnings as errors

* Update deployment/ci-cd-license-key.md

Co-authored-by: Yordan <[email protected]>

---------

Co-authored-by: Yordan <[email protected]>

Author: dimodi

deployment/ci-cd-license-key.md

@@ -136,6 +136,16 @@ Also see [Using NuGet Keys](slug:deployment-nuget#using-nuget-keys) in the artic
 
 To avoid accidental [license watermarks and notifications on your live site](slug:installation-license-key#will-telerik-ui-for-blazor-work-with-an-expired-license-key), you can fail the application build and abort deployment when there is an issue with the license key. There are two alternative ways to list the [Telerik license warning codes](slug:troubleshooting-license-key-errors#error-messages) to be treated as errors:
 
+* Add а `<TelerikLicensingStrict>` tag to the `.csproj` project file. This approach requires Telerik UI for Blazor version `9.0.0` and above, or `Telerik.Licensing` version `1.6.5` and above.
+  ````XML.skip-repl
+  <PropertyGroup>
+    <TargetFramework>net8.0</TargetFramework>
+    <Nullable>enable</Nullable>
+    <ImplicitUsings>enable</ImplicitUsings>
+    <TelerikLicensingStrict Condition="$(Configuration) == 'Release'">true</TelerikLicensingStrict>
+  </PropertyGroup>
+  ````
+
 * [Add a `<WarningsAsErrors>` tag](https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-options/errors-warnings#warningsaserrors-and-warningsnotaserrors) to the `.csproj` project file:
     ````XML.skip-repl
     <PropertyGroup>