KeyVault SDK must have the CustomHookPolicy in their pipeline

[lmazuel]

This allows the injection of kwargs raw_response_hook/raw_request_hook

FYI @johanste

[lmazuel]

Side note, there is an instance already in the generated code, but it's not plugged in the policies list:

azure-sdk-for-python/sdk/keyvault/azure-keyvault-secrets/azure/keyvault/secrets/_shared/_generated/v7_0/_configuration.py

Line 46 in 117a6f5

self.custom_hook_policy = kwargs.get('custom_hook_policy') or policies.CustomHookPolicy(**kwargs)

azure-sdk-for-python/sdk/keyvault/azure-keyvault-secrets/azure/keyvault/secrets/_shared/client_base.py

Lines 35 to 45 in 117a6f5

	config.headers_policy,
	UserAgentPolicy(base_user_agent=USER_AGENT, **kwargs),
	config.proxy_policy,
	ContentDecodePolicy(),
	config.redirect_policy,
	config.retry_policy,
	config.authentication_policy,
	config.logging_policy,
	DistributedTracingPolicy(**kwargs),
	logging_policy,
	]

[iscai-msft]

@lmazuel we have PRs out to switch all of the keyvault code to the new autorest generated code, ex here. We haven't merged these yet since we're waiting for the service to make the 7.1 swagger GA and will merge once we have that generated code. Once these are merged, this issue should be fixed as well

[lmazuel]

@iscai-msft given that KV has its own pipeline definition, a regeneration of code wouldn't be enough, unless you stop doing your own pipeline