Add support to sync k8s secret

[ritazh]

Fixes #167

Release note:

Users now have the ability to sync K8s secrets by adding secretObjects to the SecretProviderClass spec to create k8s secrets from the mounted file content

• unit test
• e2e test

Follow up items:

• docs (these will need to wait after we cut a new release)
• examples (these will need to wait after we cut a new release)
• Better handler for multiple secretsproviderclass volumes Better handler for multiple secretsproviderclass volumes #187
• Use a controller to watch secretsproviderclass status byPod field to reconcile secrets instead Use a controller to reconcile secrets #188

Updated secretsproviderclass spec:

spec:
  parameters:
    objects: |
      array:
        - |
          objectPath: "/foo"
          objectName: "bar"
          objectVersion: ""
        - |
          objectPath: "/foo1"
          objectName: "bar"
          objectVersion: ""
    roleName: example-role
    vaultAddress: http://10.0.219.186:8200
    vaultSkipTLSVerify: "true"
  provider: vault
  secretObjects:
  - data:
    - key: pwd
      objectName: foo
    - key: username
      objectName: foo1
    secretName: foosecret
    type: Opaque
status:
  byPod:
  - id: 07b8b844-797d-4fa5-9638-e93c4e5f467c
    namespace: default
  - id: 101c3595-1863-4571-8b40-d32d51691335
    namespace: default

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ritazh

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:

• OWNERS [ritazh]

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

[aramase]

/test pull-secrets-store-csi-driver-e2e-windows

[ritazh]

/test pull-secrets-store-csi-driver-e2e-windows

[aramase]

/test pull-secrets-store-csi-driver-e2e-windows

[aramase]

/lgtm

[aramase]

/lgtm