[feature request] make lxcfs configurable supportd in CRI managers for Kubernetes

[starnop]

Ⅰ. Issue Description

Currently, PouchContainer has supported resource review isolation via lxcfs, While actually in kubernetes, there is no related API to support these feature.

In order to implement this, I think we have to support these parameters in annotations in CRI manager(CRI implementation of PouchContainer).

When CRI manager deals the annotation details, it could pass these parameters to container manager, and container manager definitely implement these features very well.

So, we need to accomplish the following things:

• define the specific naming in annotations for each feature;
• implement the transformation in CRI manager and pass them to container manager.

Ⅱ. Describe what happened

Ⅲ. Describe what you expected to happen

Ⅳ. How to reproduce it (as minimally and precisely as possible)

Ⅴ. Anything else we need to know?

Ⅵ. Environment:

• pouch version (use pouch version):
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

[pouchrobot]

Thanks for your contribution. 🍻 @starnop
While we thought ISSUE TITLE could be more specific, longer than 20 chars.
Please edit issue title instead of opening a new one.
More details, please refer to https://github.com/alibaba/pouch/blob/master/CONTRIBUTING.md

[starnop]

we could have the following definition:

{"io.kubernetes.lxcfs.enabled": "true"} means we need to enable lxcfs for a container;

@allencloud WDTY?