[UMD] Switching to new coord API

[broskoTT]

Ticket

Related to #17002

Problem description

One of the many changes leading towards tt-metal using new CoreCoords, both in soc_descriptor and in umd's interface.
Due to complexity of all the maps present, the changes will be relatively small.

What's changed

• virtual_core_from_physical_core and get_virtual_coordinate_from_physical_coordinates rewritten to use translate_coord_to instead of convert_to_umd_coordinates and translate_to_noc_table_coords
• removed worker_log_to_physical_routing and physical_routing_to_virtual_routing from metal_soc_descriptor
• get_physical_tensix_core_from_logical and convert_to_umd_coordinates rewritten to use translate_coord_to
• Rewritten some get_physical_core_from_logical_core to get_physical_tensix_core_from_logical
• grayskull soc descriptor changed so that it is rowwise instead of columnwise. This matches the way it is written in UMD, and it matches other soc descriptors.
• bump umd to pull in some new changes in UMD

Checklist

All runs on brosko/soc_new_api :

• All post-commit tests : https://github.com/tenstorrent/tt-metal/actions/runs/12986193862
• Blackhole post-commit tests : https://github.com/tenstorrent/tt-metal/actions/runs/12986195849
• (Single-card) Model perf tests : https://github.com/tenstorrent/tt-metal/actions/runs/12986198348
• (Single-card) Device perf regressions : https://github.com/tenstorrent/tt-metal/actions/runs/12986201144
• (T3K) T3000 unit tests : https://github.com/tenstorrent/tt-metal/actions/runs/12986203715
• (T3K) T3000 demo tests : https://github.com/tenstorrent/tt-metal/actions/runs/12986205723
• (TG) TG unit tests : https://github.com/tenstorrent/tt-metal/actions/runs/12986207280
• (TG) TG demo tests : https://github.com/tenstorrent/tt-metal/actions/runs/12986209173
• (TGG) TGG unit tests : https://github.com/tenstorrent/tt-metal/actions/runs/12986211545
• (TGG) TGG demo tests : https://github.com/tenstorrent/tt-metal/actions/runs/12986213812

[abhullar-tt]

overall lgtm, @tt-asaigal you might want to take a look as well

[tt-asaigal]

Overall great changes! Just wondering - is the next step to have UMD accept generic coordinate systems so that we can get rid of convert_to_umd_coordinates?

[broskoTT]

Overall great changes! Just wondering - is the next step to have UMD accept generic coordinate systems so that we can get rid of convert_to_umd_coordinates?

Yes, that would be one of the goals, it is questionable how many PRs I'll have until we come to that state, the existing code is messy.
The idea is to switch everything to tt::umd::CoreCoords and not have any translation outside of it. But also reduce number of translations if makes sense (I hope this will end up being obvious at some point)

[abhullar-tt]

Thanks for starting this work out with a small PR, makes it easier to see the uplift