Local registry issues with dependencies

[lizardruss]

What happened?
When using local registry in a DevSpace project with dependencies, only some of the images can be pushed.

What did you expect to happen instead?
All images to be built and pushed.

How can we reproduce the bug? (as minimally and precisely as possible)
Using the microservices example, the second image to build will attempt to start a second local registry and fail

Local Environment:

• DevSpace Version: v6.2.0-alpha.0

Anything else we need to know?
Each dependency build tries to start a local registry with the same name, and then attempt to port-forward on the same port.

Workaround:
Configure the local registry for dependents to have different names. This will cause them to have separate ports to forward on.

node/devspace.yaml

localRegistry:
  name: node-registry

php/devspace.yaml

localRegistry:
  name: php-registry