[Bug Report]: Schema could not be accessed `az partnercenter marketplace offer plan technical-configuration package add`

### cli command

az partnercenter marketplace offer plan technical-configuration package add

### Extension version

0.2.6

### Describe the bug

`az partnercenter marketplace offer plan technical-configuration package add` results in a 400.

```
{'error': {'code': 'badRequest', 'message': 'Schema https://product-ingestion.azureedge.net/schema/configure/2022-03-01-preview2 could not be accessed'}}
```

### To reproduce

`az partnercenter marketplace offer plan technical-configuration package add ...`

### Code snippet

```Bicep

```

### Relevant log output

```Shell
{'error': {'code': 'badRequest', 'message': 'Schema https://product-ingestion.azureedge.net/schema/configure/2022-03-01-preview2 could not be accessed'}}
```

The payload names no files or tests; use the `az partnercenter marketplace offer plan technical-configuration package add` command as the entry point and reproduce the 400 response. Trace the command's schema access path, then verify the command completes without the reported “Schema ... could not be accessed” error.

Written by the indexing model from the issue text.