Update-AzConfig displays "breaking change warning" while I use it to turn it off ??!

### Description

I ask for suppression of these warnings
`Update-AzConfig -DisplayBreakingChangeWarning $false -Scope Process`

and very ironically I get

```
Upcoming breaking changes in the cmdlet 'Update-AzConfig' :
Parameter 'DisableErrorRecordsPersistence' will be deprecated, a new parameter 'EnableErrorRecordsPersistence' will be added instead. Writing error records to file system will become opt-in instead of opt-out. This change will happen around May 2024
- The change is expected to take effect in Az version : '12.0.0'
- The change is expected to take effect in Az.Accounts version : '2.X'
Note : Go to https://aka.ms/azps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.
```
I suspect if I do not use `-Scope Process` it will be only once, but hey, I want to turn off exactly what I am getting...

### Issue script & Debug output

```PowerShell
Update-AzConfig -DisplayBreakingChangeWarning $false -Scope Process

Upcoming breaking changes in the cmdlet 'Update-AzConfig' :
Parameter `DisableErrorRecordsPersistence` will be deprecated, a new parameter `EnableErrorRecordsPersistence` will be added instead. Writing error records to file system will become opt-in instead of opt-out. This change will happen around May 2024
- The change is expected to take effect in Az version : '12.0.0'
- The change is expected to take effect in Az.Accounts version : '2.X'
Note : Go to https://aka.ms/azps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.
```

### Environment data

```PowerShell
Name Value
---- -----
PSVersion 7.2.0
PSEdition Core
GitCommitId 7.2.0
OS Microsoft Windows 10.0.17763
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
Get-Module Az* did not give any output (The script is run from an Azure Runbook / Automation account)
```

### Error output

```PowerShell
No exception involved therefore cmdlet not run
```