fix: naming for services & service entrypoint

[nielstenboom]

Hi me again 😄

We ran into two bugs using the k8s hooks with a service, the bugs were as follows:

• Kubernetes would not accept the generated service name if you provide a non-official docker image (e.g localstack/localstack), Kubernetes then complains about a / being in the container name.
• The code would send entrypoint: [undefined] as the service spec, which Kubernetes would transform into [""] and that causes an error. This was not caught by the test because the actual args passed actually contained entrypoint: null. I've added that to the example.

Please let me know what you think!

[nielstenboom]

Thanks for the review @nikola-jokic ! I've implemented your suggestions 👍

[nielstenboom]

Can you please fix the linter issue

Should be fixed now after merging main into this branch 👍

It was caused by an outdated package-lock.json