feat(query): add user option: disabled

[TCeason]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

If specify DISABLED = TRUE for a user:

The user cannot log in again.

-- root user: u1 can not login
create user u1 identified by '123' with disabled=true;
-- root user: u2 can not login
alter user u2 with disabled=true;
$ bendsql -uu2 -pabc123;
Welcome to BendSQL 0.12.4-unknown.
Connecting to localhost:8000 as user u2.
Error: APIError: RequestError: Start Query failed with status 401 Unauthorized: {"error":{"code":"401","message":"AuthenticateFailure: user u2 is disabled. Not allowed to login"}}

Note

If a period of time passes, need to re-enable the user:

-- root user
ALTER USER u2 with DISABLED = FALSE;

$ bendsql -uu2 -pabc123 --query="select 'Enabled'"
Enabled

• Fixes #[Link the issue here]

Tests

• Logic Test

Type of change

• New Feature (non-breaking change which adds functionality)

---

This change is 

[drmingdrmer]

Reviewed 17 of 19 files at r1, all commit messages.
Reviewable status: 17 of 19 files reviewed, all discussions resolved (waiting on @b41sh and @flaneur2020)

[drmingdrmer]

Reviewed 2 of 19 files at r1, 2 of 2 files at r2, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @flaneur2020 and @TCeason)

[drmingdrmer]

This is not a big deal but in general, I'd suggest to use enabled in place of disabled, because a double negative user.disabled being false make it more difficult to read.

[TCeason]

This is not a big deal but in general, I'd suggest to use enabled in place of disabled, because a double negative user.disabled being false make it more difficult to read.

I got you. But this option mainly used to disable user login. So disable is directly.

If use enable, user wants to disable will write enable=false.