Split the test VolumeHosts type into one per interface

[chrishenzie]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
The fakeVolumeHost previously implemented both the KubeletVolumeHost and AttachDetachVolumeHost interfaces. This design makes it difficult to fully test the csiAttacher and csiPlugin because their behavior depends on which interface the VolumeHost implements.

kubernetes/pkg/volume/csi/csi_plugin.go

Lines 192 to 216 in c4aca30

	// set CSIDriverLister and volumeAttachmentLister
	adcHost, ok := host.(volume.AttachDetachVolumeHost)
	if ok {
	p.csiDriverLister = adcHost.CSIDriverLister()
	if p.csiDriverLister == nil {
	klog.Error(log("CSIDriverLister not found on AttachDetachVolumeHost"))
	}
	p.volumeAttachmentLister = adcHost.VolumeAttachmentLister()
	if p.volumeAttachmentLister == nil {
	klog.Error(log("VolumeAttachmentLister not found on AttachDetachVolumeHost"))
	}
	}
	kletHost, ok := host.(volume.KubeletVolumeHost)
	if ok {
	p.csiDriverLister = kletHost.CSIDriverLister()
	if p.csiDriverLister == nil {
	klog.Error(log("CSIDriverLister not found on KubeletVolumeHost"))
	}
	p.serviceAccountTokenGetter = host.GetServiceAccountTokenFunc()
	if p.serviceAccountTokenGetter == nil {
	klog.Error(log("ServiceAccountTokenGetter not found on KubeletVolumeHost"))
	}
	// We don't run the volumeAttachmentLister in the kubelet context
	p.volumeAttachmentLister = nil
	}

This is a prerequisite cleanup step for #64429.

Which issue(s) this PR fixes:
See above, this does not fix a particular issue but is a cleanup step prior to tackling the issue.

Special notes for your reviewer:
I would suggest looking at the new VolumeHost test types as a starting point, which can provide context on the other changes in the commit.

Does this PR introduce a user-facing change?:

NONE

/sig storage
/assign @Jiawei0227
/assign @jingxu97

@msau42
@saad-ali

[k8s-ci-robot]

@chrishenzie: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[chrishenzie]

/sig testing

[chrishenzie]

/retest

[k8s-ci-robot]

@chrishenzie: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-kubernetes-e2e-aks-engine-azure	9d8f994	link	/test pull-kubernetes-e2e-aks-engine-azure

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[saad-ali]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrishenzie, saad-ali

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/kubelet/volumemanager/OWNERS [saad-ali]
• pkg/volume/OWNERS [saad-ali]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment