Enable QAT key provider

[soulxu]

What this PR does / why we need it:

The qat key provider was disabled due to CI breaking #5411 (comment), now the build issue was fixed by envoyproxy/envoy#33143, so enable it again.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #5411

Special notes for your reviewer:

[istio-testing]

Hi @soulxu. Thanks for your PR.

I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[lei-tang]

/ok-to-test

[soulxu]

We probably need to wait the istio proxy update to the latest envoy.

[zirain]

wait for #5426

[ericvn]

/test release-test

[zirain]

@soulxu can you share the root cause? is there anything we can do at envoy repo to prevent this happen again?

[soulxu]

@soulxu can you share the root cause? is there anything we can do at envoy repo to prevent this happen again?

@zirain, I find some useless building parameters were added by PR. And those parameters lead to we build some shared library which qat provider key provider doesn't need actually. But I can't figure out why those build error only happened on the istio ci, since I also can't reproduce this compile error in my local.