fix(query): privilege type forward compat

[TCeason]

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

Summary

1. add ci test foreward compat test(now only test rbac)
2. UserPrivilegeType and ShareGrantObjectPrivilege deserialize use from_bits_truncate

Befero we use from_bits, in this pr, use from_bits_truncate

from_bits will cause breaking change. When add new bit, old query can not deserialize the new bit. And then return err.

https://docs.rs/enumflags2/0.7.7/enumflags2/struct.BitFlags.html#method.from_bits

https://docs.rs/enumflags2/0.7.7/enumflags2/struct.BitFlags.html#method.from_bits_truncate

I think we should ignore the new bit. So now call from_bits_truncate to deserialize bitflags.

• Fixes #[Link the issue here]

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 

[TCeason]

@everpcpc Please help to review the .github yaml and test-foreward-compat part in this pr.

[TCeason]

cc @lichuang @drmingdrmer Are there any other concerns about considering using bits_from? Through these tests added so far, I think it's safe to guarantee that the current pr will not cause a break. Please review it.

cc @BohuTANG Maybe can add a ci-cloud tag, and try to fix your warehouse?

[drmingdrmer]

Reviewed all commit messages.
Reviewable status: 0 of 11 files reviewed, 1 unresolved discussion (waiting on @lichuang, @TCeason, and @Xuanwo)

---

tests/fuse-forward-compat/util.sh line 1 at r1 (raw file):

#!/bin/bash

Do not copy, reuse util.sh. It's a burden maintaining two copies of the same function set.

[drmingdrmer]

@TCeason
IMHO, You can just add the forward compat test in the fuse-compat dir.

[TCeason]

@TCeason IMHO, You can just add the forward compat test in the fuse-compat dir.

I got you. I'm modifing it. But now this can prove that this pr not generate new break change?

[TCeason]

@TCeason IMHO, You can just add the forward compat test in the fuse-compat dir.

Done

[drmingdrmer]

@TCeason
Why do not you just re-use run_test in the util.sh but create another run_forward_test instead?
These two function does the same thing: write to version A and ready with version B.
Just update variable names run_test uses and reuse it for forward compatibility test.

[github-actions]

Docker Image for PR

• tag: pr-14501-e43569a

note: this image tag is only available for internal use,
please check the internal doc for more details.

[BohuTANG]

Test on Cloud Prod, user auth has no issue.