Store CLI history even if query starts with spaces

[ebyhr]

Description

Previously, query starting with spaces likes below wasn't stored to history.

trino>     SELECT 1;

Documentation

(x) No documentation is needed.

Release notes

(x) Release notes entries required with the following suggested text:

# CLI
* Store history even if query starts with spaces. ({issue}`12847`)

[nineinchnick]

That's the default behavior of bash, but I guess cli users don't have to know it and can be pasting queries with extra chars

[findepi]

That's the default behavior of bash

i find it very useful to be able to skip history, especially when i rely on my history to fire up queries effectively.

but I guess cli users don't have to know it

if a user is unaware of history, it doesn't matter
it they know about arrow up/down and nothing more, the change makes sense
if they want to leverage history more, like ctrl+R, i guess it may be negative.

(just my 2c)

[martint]

Why would history not be saved if the line has leading spaces? I think that's a UI inconsistency and usability issue. In particular, is seems wrong that one of these lines will get saved but the other one won't:

trino> SELECT 1;
trino>  SELECT 2;

I consider that a bug.