`Set-AzLogicapp` Name parameter does not support pipeline input

### Description

Attempting to pipe the results of a logicapp saved to a variable to `Set-AzLogicapp` requests the mandatory `Name` parameter be provided.

This is unusual pipeline behaviour given that the relevant property names are presend and `ResourceGroupName` does in fact take pipeline input.

```powershell

$logicapp = Get-AzLogicapp

$logicapp | Set-AzLogicApp -State Disabled

cmdlet Set-AzLogicApp at command pipeline position 1
Supply values for the following parameters:
(Type !? for Help.)
Name:
```

### Issue script & Debug output

```PowerShell
(gcm Get-AzLogicApp).Parameters.Name.Attributes

ExperimentName :
ExperimentAction : None
Position : -2147483648
ParameterSetName : ListWorkflows
Mandatory : False
ValueFromPipeline : False
ValueFromPipelineByPropertyName : False
ValueFromRemainingArguments : False
HelpMessage : The name of the workflow.
HelpMessageBaseName :
HelpMessageResourceId :
DontShow : False
TypeId : System.Management.Automation.ParameterAttribute
```

### Environment data

```PowerShell
Name Value
---- -----
PSVersion 7.2.1
PSEdition Core
GitCommitId 7.2.1
OS Microsoft Windows 10.0.19043
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
```
```

### Module versions

```PowerShell
ModuleType Version Name
---------- ------- ----
Script 2.7.6 Az.Accounts
Script 1.5.0 Az.LogicApp
Script 5.6.0 Az.Resources
```
```

### Error output

_No response_

Start by locating the Set-AzLogicApp implementation and its parameter metadata, then compare the Name parameter with ResourceGroupName and the behavior shown in the issue. Verify that piping a Get-AzLogicApp result supplies Name without prompting, and run the cmdlet's existing tests if available.

Written by the indexing model from the issue text.