Remove maximumWaitingRuns on designer view because Recurrence trigger does not support maximumWaitingRuns

### Severity

P1 - Critical (Blocking production)

### Describe the Bug with repro steps

Background:
In the Designer View of the Azure portal, when selecting the Recurrence trigger and enabling Concurrency control, the maximumWaitingRuns parameter is displayed.
However, it has been confirmed that the Recurrence trigger does not support maximumWaitingRuns. This limitation applies to both the Standard and Consumption plans (for the Recurrence trigger only).
We have already discussed this with PG/EEE.
Therefore, we should remove the maximumWaitingRuns parameter and update the documentation accordingly.

Current result:
"Maximum waiting runs" is displayed when Concurrency control is enabled on the Recurrence trigger.

Expect result:
"Maximum waiting runs" should **not** be displayed when Concurrency control is enabled on the Recurrence trigger.

Repro Step:
Open Azure portal
Select Logic App
Create and select workflow
Set Recurrence trigger
Enable Concurrency control

ASK:
Could you please remove maximumWaitingRuns (for the Recurrence trigger only)?

### What type of Logic App Is this happening in?

Standard (Portal)

### Are you experiencing a regression?

_No response_

### Which operating system are you using?

Windows

### Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

### Workflow JSON

```json
{
"definition": {
"$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
"contentVersion": "1.0.0.0",
"actions": {
"Delay": {
"type": "Wait",
"inputs": {
"interval": {
"count": 5,
"unit": "Minute"
}
},
"runAfter": {}
}
},
"outputs": {},
"triggers": {
"Recurrence": {
"type": "Recurrence",
"recurrence": {
"interval": 3,
"frequency": "Minute"
},
"runtimeConfiguration": {
"concurrency": {
"runs": 1,
"maximumWaitingRuns": 11
}
}
}
}
},
"kind": "Stateful"
}
```

### Screenshots or Videos

_No response_

### Environment

- Browser Microsoft Edge and so on

### Additional context

_No response_

Search the Designer View code for maximumWaitingRuns and the Recurrence trigger handling. Verify how concurrency settings are rendered for Recurrence in Standard and Consumption plans, then update the related documentation. Done means maximum waiting runs is not displayed for Recurrence while remaining available for supported triggers, with documentation matching the behavior.

Written by the indexing model from the issue text.