feat: add helm config to enable deleteAccessPointRootDir

[KarstenSiemer]

Is this a bug fix or adding new feature?
This is a new feature. (Also includes very minor fix for the log level in the controller deployment for the log level)
What is this PR about? / Why do we need it?
It adds the ability to enable the --delete-access-point-root-dir flag on the controller deployments efs-plugin sidecar.
What testing is done?
Talked about the flag in #411
I'd suggest to use it like this in helm. If the value is set to false or is omitted, then the flag will be set to false. If the value is set to true, then it will be set to true. This way we don't have to change the chart again, if the default behavior of the flag will be changed, like if it would default to true.
Merged this pr in my fork and rolled it out in a cluster.

[k8s-ci-robot]

Welcome @KarstenSiemer!

It looks like this is your first PR to kubernetes-sigs/aws-efs-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/aws-efs-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @KarstenSiemer. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[KarstenSiemer]

/assign @leakingtapan

[wongma7]

/ok-to-test

[KarstenSiemer]

lessened coverage makes sense in this case. But do we want to write tests for the helm chart?
How do we want to proceed with this pr?

[wongma7]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: KarstenSiemer, wongma7

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 [wongma7]

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

[wongma7]

@KarstenSiemer don't worry about ocveralls, it's bugged sometimes, I will merge once the other Required tests pass.