Binary in `/bin/` folder to follow upstream

Summary

binary for elasticsearch_exporter is not available on container's $PATH for execution.

Steps to reproduce

Deploy this container in a BigBang cluster utilizing upstream and bitnami examples.

What is the current bug behavior?

Container fails to starts enters CrashLoopBackoff phase.

What is the expected correct behavior?

elasticsearch_exporter starts and is collecting info and displaying metrics on port 9114.

Relevant logs and/or screenshots

Error: failed to create containerd task: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/bin/elasticsearch_exporter": stat /bin/elasticsearch_exporter: no such file or directory: unknown
Error: failed to create containerd task: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "elasticsearch_exporter": executable file not found in $PATH: unknown

Possible fixes

Update the Dockerfile to match that of the upstream Dockerfile so that the binary is available in /bin/ and therefore the container's $PATH.

Defintion of Done

• Bug has been identified and corrected within the container