Dockerfile: copy redpanda-connect binary into /usr/sbin folder instead of root (/) for CI/CD usage

Trying to use the redpanda-connect official Docker image in a CI/CD pipeline in GitLab (for linting and unit-testing purposes), however since the redpanda-connect binary is not in a folder of $PATH I cannot execute it:

From within a shell of redpanda-connect container:

/ $ ls
bin               dev               home              lib64             redpanda-connect  sys               usr
connect.yaml      etc               lib               proc              root              tmp               var
/ $ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
/ $ which redpanda-connect
/ $ 

It would be greatly appreciated if the Dockerfile would be changed to copy the binary into /usr/sbin (or any other folder in $PATH (as well as modifying the entrypoint to ENTRYPOINT ["redpanda-connect"]).

I don't think this would introduce a breaking change?

Inspect the Dockerfile and the current container entrypoint, then build the official image to check where redpanda-connect is placed and how it is invoked. Done means the binary is available through the container's PATH and the requested entrypoint behavior works for CI/CD use.