Keyvaults - Securing secrets parameter by using object

[vgaupset]

Change

Converting secrets parameter to secure object. The array type does not have the secure option and will therefore be displayed in plaintext in Azure portal (in deployments or export template).

Type of Change

Please delete options that are not relevant.

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
  (Due to change from array to object)

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• My corresponding pipelines / checks run clean and green without any errors or warnings
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (readme)
• I did format my code

[ghost]

All CLA requirements met.

[AlexanderSehr]

Please also update the parameters.json file.

"secrets": {
    "value": {
        "secureList": [
            {
                "name": "secretName",
                "value": "secretValue",
                "contentType": "Something",
                "attributesExp": 1702648632,
                "attributesNbf": 10000,
                "roleAssignments": [
                    {
                        "roleDefinitionIdOrName": "Reader",
                        "principalIds": [
                            "<<deploymentSpId>>"
                        ]
                    }
                ]
            }
        ]
    }
}

[AlexanderSehr]

Hey @vgaupset, thanks for the contribution. Just checked it out locally and suggested a few minor changes (rename + parameter file). Thanks for you contribution :)

[vgaupset]

@MrMCake No problem :) I have changed the PR in compliance with requested changes.