Initial Admin password stored in secrets manager fails to authenticate.

Nobody has claimed this yet.

Thanks for this awesome library!

I created a new AD using the `AwsManagedMicrosoftAdR53` pattern and the default domain. The login test fails initially using the password stored in secrets manager and only works after it is reset from the console.

Is this the expected behavior (does it need a reset)? Is it better to automate the password reset it as part of the stack creation?

```
const vpc = new Vpc(this, 'ControlPlaneVpc', {});
const ad = new authentication.AwsManagedMicrosoftAdR53(
this,
'AwsManagedMicrosoftAdR53',
{
vpc: vpc,
}
);
```

And here is the code I am using to test the authentication.

```
$UserName = 'Admin'
$Password = 'MY_PASSWORD' #original password from secrets manager fails, works after resettting and using new password
$Domain = 'domain.aws'

Add-Type -AssemblyName System.DirectoryServices.AccountManagement
$ct = [System.DirectoryServices.AccountManagement.ContextType]::Domain
$pc = New-Object System.DirectoryServices.AccountManagement.PrincipalContext $ct,$Domain
$pc.ValidateCredentials($UserName,$Password)
```

Start at the AwsManagedMicrosoftAdR53 construct entry point and trace how the initial Admin password is stored in Secrets Manager and used by the directory. Compare that behavior with the console reset flow; done means determining whether the generated credential should authenticate immediately and documenting or implementing the agreed creation-time behavior.

Written by the indexing model from the issue text.