Fix time fields of rows from GetClusterMembers

[rodrigozhou]

What changed?
In GetClusterMembers, fix the time fields, ie., call date time converter.

Why?
The times are stored in UTC in DB, but when reading, the time zone might not be set correctly. Calling the date time converter fixes it.

How did you test it?
Existing tests.

Potential risks
None.

Is hotfix candidate?
No.

[yycptt]

Can we add a test for to prevent future regression?

[rodrigozhou]

@yycptt I found this issue because I'm making a change in the SQLite driver connection config and unit tests failed.

In practice, those conversions calls are unnecessary because the date time are already stored in UTC. However, I'm changing a config related to the date time format to store in SQLite to ISO format, and go time.Parse doesn't translate "+00:00" to the internal time.UTC location, which caused the test to fail.

Currently, it's writing in the format "2006-01-02 15:04:05.999999999 -0700 MST", ie., it contains the 3-letter timezone code. In our case, it contains the "UTC" string.

I'm changing to the format "2006-01-02 15:04:05.999999999-07:00", and because it doesn't contain the 3-letter timezone code, time.Parse doesn't set the time zone as time.UTC location, but as time zone location equivalent to it (ie., +00:00).