Starting new node (with new location) doesn't delete old container

[morrigan]

Describe the bug
It seems like "run own node" should create a new container each time rather than reuse old ones, especially if new path location is set.

To Reproduce
Steps to reproduce the behavior:

1. Create new BN
2. Delete ChainGuardian app data
3. Open CG, no beacon nodes, click to add new one
4. Customize new beacon node with for example new data path and start it
5. Old container is used with the old location

Expected behavior
A fresh new container with new path location or if existing is found ask to delete.

Desktop:

• OS: Windows 10
• Network Pyrmont
• Chain Guardian Version 0.5.2