chore: Use timestamp instead of random number for test resource names

[manupedrozo]

Move to use timestamps when generating test resource names.
The current approach can generate duplicate names which cause failures for the resources that require unique names.
It is also confusing to see duplicates in the UI when debugging issues.

Link to any related issue(s):

Type of change:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as
  expected)
• This change requires a documentation update
• If changes include removal or addition of 3rd party GitHub actions, I updated our internal document. Reach out to the APIx Integration slack channel to get access to the internal document.

Manual QA performed:

• cfn invoke for each of CRUDL/cfn test
• Updated resource in example
• Published to AWS private registry
• Used the template in example to create and update a stack in AWS
• Deleted stack to ensure resources are deleted
• Created multiple resources in same stack
• Validated in Atlas UI
• Included screenshots

Required Checklist:

• I have signed the MongoDB CLA
• I have added tests that prove my fix is effective or that my feature works
• I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
• I have added any necessary documentation (if appropriate)
• I have run make fmt and formatted my code
• For CFN Resources: I have released by changes in the private registry and proved by change
  works in Atlas

Further comments

[manupedrozo]

Only organization tests failing - known issue: CLOUDP-332705

[lantoli]

is it in seconds or milliseconds? in case we need to add a random to timestamp.
thinking in case of publishing a resource to multiple regions, script would be executed multiple times at almost the same time

[manupedrozo]

Good catch! Switching to ms here b7688b9

[AgustinBettati]

LGTM

[AgustinBettati]

from PR description was curious how we got to this work, is there any related CLOUDP or related PR in which we detected this issue?

[manupedrozo]

Saw tests failing due to duplicated names while merging sdk updates. Need to re-run in those cases to roll the dice again.

[lantoli]

I think this will work fine in Linux and GHA, but won't work in Mac:

# Expected: ct-alert-config-1733356800123
# Actual:   ct-alert-config-1733356800N
                                    ↑
                          literal "N", not milliseconds

The %3 part is ignored, and %N becomes a literal "N" character.

not sure if keep the random, maybe bigger 😅 or timestamp in seconds + random, e.g.:

 projectName="cfn-bot-access-list-$(date +%s)$(1 + RANDOM % 10000)"

[manupedrozo]

Sad. Going with seconds + random. Thanks!

[EspenAlbert]

Ty! However, would be awesome if we also supported reading the projectName from an env-var so it is simpler to debug and test locally