fix: adds back support for legacy AllowPackageTelemetry (#18644)

Due to an unfortunate mistake in the Umbraco.Cms.Targets generated JSON schema, we alluded to supporting `allowPackageTelemetry` in the JSON files, however the backend didn't support this.

src/Umbraco.Core/Manifest/PackageManifest.cs

@@ -12,6 +12,9 @@ public class PackageManifest
 
     public bool AllowTelemetry { get; set; } = true;
 
+    [Obsolete("Use AllowTelemetry instead. This property will be removed in future versions.")]
+    public bool AllowPackageTelemetry { get; set; } = true;
+
     public required object[] Extensions { get; set; }
 
     public PackageManifestImportmap? Importmap { get; set; }

src/Umbraco.Infrastructure/Services/Implement/PackagingService.cs

@@ -353,7 +353,7 @@ public class PackagingService : IPackagingService
             }
 
             // Set additional values
-            installedPackage.AllowPackageTelemetry = packageManifest.AllowTelemetry;
+            installedPackage.AllowPackageTelemetry = packageManifest is { AllowTelemetry: true, AllowPackageTelemetry: true };
 
             if (!string.IsNullOrEmpty(packageManifest.Version))
             {

src/Umbraco.Web.UI.Client/src/json-schema/umbraco-package-schema.ts

@@ -27,6 +27,13 @@ export interface UmbracoPackage {
 	 */
 	allowTelemetry?: boolean;
 
+	/**
+	 * @title Decides if the package sends telemetry data for collection
+	 * @default true
+	 * @deprecated Use allowTelemetry instead
+	 */
+	allowPackageTelemetry?: boolean;
+
 	/**
 	 * @title Decides if the package is allowed to be accessed by the public, e.g. on the login screen
 	 * @default false