feat(clap_complete): Support hiding long flags and their long aliases

[shannmu]

Based on PR: #5549
Related issue: #3951

Works in this PR

• refactor: Add CompletionCandidate to replace (OsString, Option<StyledStr>). There will be a new field named visible for CompletionCandidate. If we don't need this struct, there will be a type (OsString, Option<StyledStr>, bool).
• Support hiding long flags and their long aliases. The specific behavior is reflected in the differences between the test commit and the feat commit.

[shannmu]

In the process of modifying the code, I feel that CompleteCandidate has made the code more complex. If it's just to add the visible field, should I remove the refactor commit to get this PR merged faster? (Previously, I hoped to use CompleteCandidate to replace ((OsString, Option, bool)), making the code simpler and adding other fields more centralized if we had to).

[epage]

In the process of modifying the code, I feel that CompleteCandidate has made the code more complex. If it's just to add the visible field, should I remove the refactor commit to get this PR merged faster? (Previously, I hoped to use CompleteCandidate to replace ((OsString, Option, bool)), making the code simpler and adding other fields more centralized if we had to).

I think its worth keeping. Overuse of tuples can make the code confusing. We were already pushing the use of tuples and this would absolutely break it.

Using a struct also offers us more API stability for when we go live with this.

[epage]

Thanks for the updates! This is looking great and look forward to the next round of improvements!

[epage]

Thanks!