Actually, i found this myself as well, got frustrated, thought something was wrong with my scripts causing these quotes, but no, apparently it is caused by the shell itself, there is some setting (quote styling) that has been turned on in GNU utils by default since some version.
If you use: ls --quoting-style=literal you will see that the quotes disappear,
edit - i just see that you use some 'exotic' lf commands (never heard of this), this could also be the cause for the default use of quotes.
The quotes are because the filename includes spaces. When entering filenames with spaces you have to quote the name (or escape the spaces) and the default with ls is to do the same. If they were not quoted you might think you have a file called Powered and another call on. I know it is obvious in the case you show, but might not be in other cases, particularly if you started adding mulitple spaces. Suppose for example the directory contained just one file called Powered on at 2021-02-212108.db Powered on at ....
Without the quotes it is unclear whether there is one file or two.