logfiles: add closing timestamp in "User Selected Bookmap time zone"

[jdnicholas2004]

1) Suggest adding a closing timetamp to logfiles in the "User's Bookmap timezone".

When responding to support requests it would be useful if the logfiles included a closing timestamp in the User's Bookmap timezone just as they currently include an initialisation timestamp in the user's Bookmap timezone.

Suggest adding the closing timestamp as the next line after the opening timestamp to make it easy for users to visually check the logfiles for inclusion of a period of relevance to a support request.

2) Tweak the formatting of the User Bookamp timezone timestamps to make them more readable. 

There are minor concatenation/formatting issues with timestamps throughout the logfiles that affect readability. For this enhancement request I'm only suggesting changes to the User's Bookmap timezone timestamps.

Add a bit of whitespace to improve readability and indicate the day of week. Alternatively, add a human-friendly timestamp re-write as an append to the end of the existing logfile entry.

I expect most Traders thing in terms of "I think I fired up bookmap just before the pre-market open on Friday morning".
A timestamp format that reflects that would improve readability/

EXAMPLE:

Current initialisation timestamp in User's Bookmap timezone:

20251121 08:52:10.213(UTC) INFO: [Date and Time](main|34) User selected Bookmap time zone current time: 2025-11-21T03:52:10.213529900-05:00[America/New_York]

More human readable would be something like (using the re-write + append method):

20251121 08:52:10.213(UTC) INFO: [Date and Time](main|34) User selected Bookmap time zone current time: 2025-11-21T03:52:10.213529900-05:00[America/New_York] (Friday 21 Nov 2025 03:52 am America/New_York)