fix: container name conflict

[MaxSiominDev]

I haven't forgotten about:

• Tests
• Changelog
• Documentation
  • JavaDoc was written
• Commit messages comply with the guideline
• Cleanup the code for review. See checklist

Related issues:

[Copilot]

Pull request overview

This PR adjusts the Tarantool v3 Testcontainers implementation to avoid Docker container name collisions by no longer force-setting the container name during container creation.

Changes:

• Removed cmd.withName(this.node) from Tarantool3Container.configure() so container names are not pinned to the node value by default.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ArtDu]

Describe why you need it? what is purpose of change? what needs to make conflict?

[MaxSiominDev]

Describe why you need it? what is purpose of change? what needs to make conflict?

I am trying to fix flaky tests (tntp-7314). As far as I understand, the underlying reason for the occasional failures is container name conflict. Original test randomizes container name using UUID, but here, the name is replaced and not random anymore. Hence we have confict, if old container is still running and new container is already started, they have the same name and tests fail due to docker error as it cannot run multiple containers with identical names at the same time