Limit number, memory and cpu of services container for docker runners

What does this MR do?

This MR add CPU and Memory limitations to service. It also add a maximum number of service per job.

Why was this MR needed?

Currently gitlab runner user, launch multiple java service per job which exhaust all runner ressource. We need to cold reboot runner to recovier it.

Are there points in the code the reviewer needs to double check?

Maybe, I try to add some test in executor_docker_test.go, but I'm a go noob and It was too hard for me to add test. If you have any clue / template ?

Does this MR meet the acceptance criteria?

• Documentation created/updated
• Added tests for this feature/bug
• In case of conflicts with master - branch was rebased

What are the relevant issue numbers?

Closes #3767