UMD API redesign changes

[broskoTT]

There is an ongoing push for redesigning UMD's API.
Related design diagram can be found here: https://docs.google.com/drawings/d/1-m1azdsBqMA0A6ATYRMfkhyeuOJuGCEI62N5a96LXj0/edit

These changes will ultimately lead to cleaner code, less code in the clients, abstract even more TT hardware specific constants, and offer defaults for larger part of current mandatory configuration.

Ongoing api redesign changes in UMD can be tracked here: https://github.com/tenstorrent/tt-umd/issues?q=is%3Aissue+is%3Aopen+label%3A%22api+redesign%22

I'll use this issue as a tracker for tt_metal side of changes aligning with the new API.