Fixes issue #585 ( bug in io.timestamp2datetime )

[ehennestad]

Fix #585 ( bug in io.timestamp2datetime )

Some dates were assigned wrongly when Day, Month and Year are set individually, as the datetime object internally/silently adjusts month if day is not valid

Motivation

What was the reasoning behind this change? Please explain the changes briefly.

How to test the behavior?

Show here how to reproduce the new behavior (can be a bug fix or a new feature)

Checklist

• Have you ensured the PR description clearly describes the problem and solutions?
• Have you checked to ensure that there aren't other open or previously closed Pull Requests for the same change?
• If this PR fixes an issue, is the first line of the PR description fix #XX where XX is the issue number?

[bendichter]

Looks great! Could you add a check demonstrating that the bug you found earlier is fixed?

[ehennestad]

NWBDefaultStringFormat = "uuuu-MM-dd'T'HH:mm:ss.SSSSSSZZZZZ";

testDate = datetime(2024, 8, 31, 'TimeZone', 'local'); % Start date: January 1st
testDate.Format = NWBDefaultStringFormat;
testDateAsString = string(testDate);

io.timestamp2datetime(testDateAsString)

ans = 

  datetime

   31-Aug-2024

I will also be adding a unittest in another PR that test all dates for a complete calendar year

[bendichter]

Could you include the test in this PR? That's how we generally package PRs.

[bendichter]

@ehennestad Generally, the tests should include a snippet of code that failed previously and passes now. There are a lot of tests here now but I don't think I see the specific failure mode you mentioned in the bug report here.