bugfix(accesslog): allow different provider between modes

[j2gg0s]

Please provide a description of this PR:

Take workload's mode into consideration, when compute inScopeProviders.
So, we can allow user config different access log providers for different mode.

This maybe what we expected.

Please check any characteristics that apply to this pull request.

• [] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

[istio-testing]

Hi @j2gg0s. 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.

[zirain]

this seems related to #39521

[j2gg0s]

this seems related to #39521

Yes, it is related but not same. This PR don't change current logic and just fix obvious unexpected behavior.

[zirain]

this seems related to #39521

Yes, it is related but not same. This PR don't change current logic and just fix obvious unexpected behavior.

I think the root case is multi accesslogging not working, let's hold this first, WDYK?

[j2gg0s]

Yes, two PR is conflict

But if we want to change Telemetry's AccessLogging behavior, Maybe it's better to define what we expected before coding.

one Telemetry has many AccessLoging，one HCM also has many access_log.
one AccessLogging has many providers, how we map this to envoy's HCM?

[istio-testing]

@j2gg0s: PR needs rebase.

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.

[istio-policy-bot]

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2022-06-30. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.