Expose more creation functions for MeshDevice, change SubMesh ownership

[sminakov-tt]

Ticket

Problem description

I'm integrating MeshDevice into TT-NN, trying to make all python code to always use MeshDevice 1x1 instead of single device APIs. To make MeshDevice APIs compatible, we need a way to create a single MeshDevice with specifying device id.
Moreover, we need an ability to create MeshDevice 1x1 for each of multiple device ids to fully mimic CreateDevices API exposed to python. Creating MeshDevices 1 by 1 for each device id is not equivalent to creating/closing them at the same time (causes fails in inividual calls to metal's CreateDevice CloseDevice). So I added a helper function to create a common mesh device and then create submeshes out of it. This presents a new ownership issue, because the parent mesh device must be kept alive longer than the children devices, however the current python code wasn't designed to handle that. So this PR inverts ownership relationship - each submesh keeps a shared_ptr to the parent mesh, ensuring that its being kept alive until the submesh is destroyed.

What's changed

Added new creation functions for MeshDevice
Changed the ownership model, parent MeshDevice doesn't keep submeshes meshes alive, but the submeshes keep the parent one alive. I think it makes some sense and simplifies MeshDevice::close(), but I'm open to discussion on possibly better ways to achieve the goal.
Removed the usages of get_submeshes method.

Checklist

• All post commit CI passes
• New/Existing tests provide coverage for changes

[omilyutin-tt]

I'm wondering if this needs to be map?

[sminakov-tt]

I made it a map to mimic CreateDevices, it simplifies the migration process

[cfjchu]

neat idea to invert the ownership