fix(api): 🐛 update API version handling in ApiOperationOperations

* Set a fixed `apiVersion` to "2024-05-01".
* Adjusted the logic to use the new `apiVersion` instead of the client’s version.
* Ensured proper tracing functionality remains intact.

Author: Update Parameters Pipeline

src/ApiManagement/ApiManagement.Management.Sdk/Generated/ApiOperationOperations.cs

@@ -682,9 +682,9 @@ internal ApiOperationOperations (ApiManagementClient client)
             {
                 throw new Microsoft.Rest.ValidationException(Microsoft.Rest.ValidationRules.CannotBeNull, "this.Client.SubscriptionId");
             }
-
-            // Tracing
-            bool _shouldTrace = Microsoft.Rest.ServiceClientTracing.IsEnabled;
+			string apiVersion = "2024-05-01";
+			// Tracing
+			bool _shouldTrace = Microsoft.Rest.ServiceClientTracing.IsEnabled;
             string _invocationId = null;
             if (_shouldTrace)
             {
@@ -710,7 +710,7 @@ internal ApiOperationOperations (ApiManagementClient client)
             _url = _url.Replace("{subscriptionId}", System.Uri.EscapeDataString(this.Client.SubscriptionId));
 
             System.Collections.Generic.List<string> _queryParameters = new System.Collections.Generic.List<string>();
-            if (this.Client.ApiVersion != null)
+            if (apiVersion != null)
             {
                 _queryParameters.Add(string.Format("api-version={0}", System.Uri.EscapeDataString(this.Client.ApiVersion)));
             }