Azure Key Vault AddSecret validation mismatch

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

Adding a secret using `AddSecret` overloads that do not take a ResourceName but only the secret name will fail to deploy due to some valid secret names not being valid resource names.

For example trying to have hierarchical secrets "MySection--MySecret", the problem being the double dash.

### Expected Behavior

Resource name should either be altered to match resource naming rules or at least the affected overloads documentation should be updated to indicate this limitation and point the user to use overloads that do take a ResourceName.

### Steps To Reproduce

```
var builder = DistributedApplication.CreateBuilder(args);
var testParam = builder.AddParameter("TestParam", true);

keyVault = builder.AddAzureKeyVault("key-vault");
keyVault.AddSecret("MySection--MySecret", testParam);
```

### Exceptions (if any)

_No response_

### .NET Version info

10.0.0

### Anything else?

_No response_