#17477: Move SmallVector and ShapeBase to re-use within Metal

[omilyutin-tt]

Ticket

#17477

Problem description

TT-distributed requires ND shapes in Metal. Instead of having our own, moving ShapeBase and SmallVector into Metal.

What's changed

• Moved ShapeBase and SmallVector into Metal. SmallVector really should be part of our "stl" library, so I put it there for now. I used ttsl namespace - my goal is to replace tt::stl as it is shorter and easier to type, also avoids confusion if anyone attempts to use stl::.

Checklist

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

[omilyutin-tt]

I'd want to do any renames in follow up PRs. Pending conversation on this one.

[omilyutin-tt]

@ayerofieiev-tt @sminakov-tt please let me know your opinion here. My plan is to subclass ShapeBase to represent MeshShape, then implement a set of libraries for multi dimensional container, device coordinates, iterator, range. Ideally also re-use that for Core* libs.

We can also move Shape and Alignment into Metal, but I think we can hold on with that. These are more specific to working with Tensors.

[ayerofieiev-tt]

SmallVector is fine to move

ShapeBase is ooookay to move
What about Shape?

[omilyutin-tt]

What about Shape?

No strong opinion here, but my mental model for Shape is that it is a Tensor shape. I'd want to subclass ShapeBase for MeshShape: methods like volume(), rank(), to_array_4D() that are added by Shape sound like they assume we are talking about tensors.