[Filebeat] Support Kubernetes Deployment (not only Daemonset)

[operatorequals]

Describe the feature:

Filebeat can be seen as a log collector not only for underline Kubernetes Node resources, but also able to collect logs through the network, AWS, etc.

By assigning Filebeat only to Daemonsets though the available Helm Chart, one cannot use it as an independent and scalable Deployment, which has some use cases as well.

Specifically, a deploymentType: [Daemonset|Deployment] YAML value (defaulting with Daemonset for compatibility), could be used to determine the type of deployment.
Then all Deployment specific values (such as .spec.replicas) can be selected by deployment.spec.replicas YAML directive.

Describe a specific use case for the feature:

Filebeat can be used as a Deployment when it is used to collect AWS logs, with the AWS module.

The issue I came across is the need for scalability for collection of Cloudtrail logs of a very heavily used AWS account, and the Filebeat Daemonset (in my 3 worker cluster) is always lagging behind as it cannot process logs as fast as they are produced.