File name of zip-archives alternates between 1 and 2 digits

[andgdk]

Brief bug description

The file name of zip-archives generated with timestamps could be improved to keep a consistent number of digits.
Running a backup at between 12:00 and 12:09
results in a file name of e.g.
2024-11-12-12-8-backup-ENVIRONMENT-ID but should likely be
2024-11-12-12-08-backup-ENVIRONMENT-ID.

Ensuring lower digits to start with 0 guarantees the zip archives to be in order of their creation when sorting files alphabetically in a file explorer or consuming archives in automations that relay on the file name.

Repro steps

1. Time the following execution to happen between a full hour and 9 minutes past the hour.
2. Execute npx @kontent-ai/data-ops@latest environment backup --environmentId=<environment-id> --apiKey=<Management-API-key>
3. Observe the file name of the zip-archive.

Expected behavior

Consistent alphabetical and historical order.

Test environment

• Windows 11
• Node 22.10.0
• Node uses a 24 h scheme

Additional context

This is a minor issue, being the purpose of documentation.
It has not been tested if this also applies to months or days (or hours - getting up to late xD).

Screenshots

No response

[IvanKiral]

Thanks for the issue :) we will look at this later as it is a minor issue, in the meantime I will set the appropriate tags for this :)