Fallback output method in case of retry limit is exceeded

**Is your feature request related to a problem? Please describe.**
In the event of an error when sending logs to elasticsearch, there are two possible behaviors: the log is discarded or fluentbit continues indefinitely to try to send it again. In case the log is a malformed json ES will never accept it and the pod tries to send it to infinity. (ex: https://github.com/wongnai/kube-slack/issues/51 )

**Describe the solution you'd like**
I would like to be able to configure the maximum number of attempts to send before discarding and possibly be able to configure an alternative destination of the logs that can not be sent. (es: S3, log folder...)

**Describe alternatives you've considered**
Actually we use "fluentbit.io/exclude: true" annotation on pod that generates malformed json to avoid this problem.

Ref: https://github.com/fluent/fluent-bit/issues/1098