Provide a sidecar to fetch information from Kubernetes

# Describe the feature you'd like to have #

There should be a sidecar that can be used to request information from Kubernetes (or any other CO) that is used by the provisioner and node-plugins.

# What is the value to the end user? (why is it a priority?) #

Currently the provisioner and node-plugins use a Kubernetes client to fetch extra information from the Kubernetes environment. This makes it impossible to use certain features (Topology based provisioning, Vault Tokens encryption) on non-Kubernetes container orchestration platforms.

# How will we know we have a good solution? (acceptance criteria) #

The Ceph-CSI provisioner and node-plugins should not connect to Kubernetes directly anymore.

# Additional context #

See conversations in #1743

Start by reading the conversations in #1743 and locating how the provisioner and node-plugins currently use a Kubernetes client to fetch extra information. Define the sidecar's request boundary for Kubernetes or other container orchestration platforms, then verify the acceptance criterion that the provisioner and node-plugins no longer connect to Kubernetes directly.

Written by the indexing model from the issue text.