Decouple containerization logic from environment

[deepakn97]

Describe the feature

In the current codebase, communicate and read methods are part of the environment submodule. This increases the complexity of the environment codebase and limits extensibility when supporting different types of containers.
The proposal is to move the containerization logic to a new module and provide abstract implementations for new container types. It is also worth exploring the use of SWE-Rex, although it is unclear whether they support GPU passthrough.

Potential Solutions

One potential solution:

1. Create a containers module in mlgym package.
2. Move communicate, communicate_with_handling, read_with_timeout, interrupt, and other communication-related functions to the new containers module.
3. If possible, create an abstraction for adding new containers.