fix: remove ulimit when re-creating container

[deviantony]

This PR sets the ulimit associated to a container to null when re-creating a container instead of inheriting it from the previous container configuration.

This should solve the issue that happens when running k2d under Podman and creating services (that re-creates container under the hood).

As setting ulimits is not supported by Kubernetes natively this should not be a breaking change.

[deviantony]

Removing the ulimit leads to another error:

ERROR	controller/controller.go:204	unable to update container	{"error": "unable to create container: Error response from daemon: container create: running container create option: names must match [a-zA-Z0-9][a-zA-Z0-9_.-]*: invalid argument", "request_id": "fbf0acd6-41bb-48ba-8254-7cf7bd7a5a65"}

I believe there is something wrong with inheriting the configuration from a previous container using Podman.

[deviantony]

Closed as this might not be required, the issue is not present on a "standard" deployment of Podman: #68 (comment)