add jobsToFetch parameter to azure pipelines docs (kedacore#1082)

Co-authored-by: Jorge Turrado Ferrero <[email protected]>

content/docs/2.10/scalers/azure-pipelines.md

@@ -31,6 +31,8 @@ triggers:
       demands: "{demands}"
       # Optional: Demands of jobs must exactly match the capabilities the trigger defines
       requireAllDemands: false 
+      # Optional: How many jobs to fetch for the pool in the API (default: 250)
+      jobsToFetch: "{jobsToFetch}"
     authenticationRef:
      name: pipeline-trigger-auth
 ```
@@ -46,7 +48,8 @@ triggers:
 - `activationTargetPipelinesQueueLength` - Target value for activating the scaler. Learn more about activation [here](./../concepts/scaling-deployments.md#activating-and-scaling-thresholds).(Default: `0`, Optional)
 - `parent` - Put the name of the ADO agent that matched the ScaledObject. e.g. mavenagent-scaledobject may have an initial deployment called "mavenagent-keda-template"; this is the deployment that is made offline. This name is provided to the initial deployment as the environment variable "AZP_NAME"
 - `demands` - Put the demands string that was provided to the ScaledObject. This MUST be a subset of the actual capability list the agent has. e.g. `maven,docker`
-
+- `jobsToFetch` - The number of the jobs that KEDA will fetch for the pool from Azure Pipeline API (Default: `250`, Optional)
+- 
 > 💡 **NOTE:** You can either use `poolID` or `poolName`. If both are specified, then `poolName` will be used.
 
 ### Authentication Parameters