AWS SSM Run Command issue with SNS Notifications

**Describe the bug**

Error raised by [AWS Systems Manager](https://docs.aws.amazon.com/systems-manager/index.html) [SendCommand](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_SendCommand.html) when the Run Command task includes SNS Notifications

**To reproduce**

1- Create a task using the AWS SSM Run Command
2- Setup the SNS Notifications
3- Run the pipeline

**Expected behavior**

API should not raise parameter errors

**Screenshots**

**Your Environment**

- On-prem or cloud based?: Cloud
- Azure DevOps version: [Sprint 225](https://learn.microsoft.com/azure/devops/release-notes/2023/sprint-225-update)
- AWS Toolkit for Azure DevOps version: 1.13.0

**Additional context**

Toolkit is sending wrong parameters to AWS Systems Manager SendCommand API:

Value 'command' at 'notificationConfig.notificationType' failed to satisfy constraint: Member must satisfy enum value set: [Command, Invocation];
Value '[all]' at 'notificationConfig.notificationEvents' failed to satisfy constraint: Member must satisfy constraint: [Member must satisfy enum value set: [All, Success, Cancelled, InProgress, TimedOut, Failed]]

**AWS Document**

Start by reproducing the AWS SSM Run Command task with SNS Notifications in a pipeline, then compare the parameters sent to the SendCommand API with the AWS documentation. Check the notificationConfig notificationType and notificationEvents values against the reported enum errors. Done means the pipeline runs without parameter validation errors.

Written by the indexing model from the issue text.