feat(query): Support check password policy when login

[b41sh]

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

Summary

Briefly describe what this PR aims to solve. Include background context that will help reviewers understand the purpose of the PR.

• UserInfo Add the following fields for password-related information verification
  • history_auth_infos: Vec<AuthInfo>: Recently changed history passwords, used to detect whether the newly changed password is repeated with the history passwords.
  • password_fail_ons: Vec<DateTime<Utc>>: The time of the most recent failed login with wrong passwords, used to detect whether the number of failed logins exceeds the limit, if so, the login will be locked for a while.
  • password_update_on: Option<DateTime<Utc>>: The time of the last password change, used to check if the minimum allowed time has been exceeded when changing the password, and to check if the maximum time that must be changed has been exceeded when login.
  • lockout_time: Option<DateTime<Utc>>: Login lockout time, records the end time of login lockout due to multiple password fails.
• when changing the password, determine whether the minimum number of days is exceeded and whether the password is repeated with the historical passwords.
• When login, determine whether the maximum number of fails has been exceeded, whether the login is locked, and whether the maximum number of days to change the password is exceeded.

Fixes #13994

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is 

[drmingdrmer]

The explanation for each field in the PR description is very useful. They should be part of the field comment. So that

Reviewed 13 of 29 files at r1, all commit messages.
Reviewable status: 13 of 29 files reviewed, all discussions resolved (waiting on @sundy-li)

[BohuTANG]

@soyeric128 For documents. Thanks!