Device resource reservations in KMD

[pjanevskiTT]

Device resource reservation is going to be implemented in https://github.com/tenstorrent/tt-kmd. The point of this feature is to enable two separate workloads to happen on a chip, or enable some utility things to happen on a chip without interfering with workload (X280 use case)

API for resource reservation is going to be exposed to UMD using few ioctl calls

1. RegisterReservation (Type, arg0, arg1, ....) => reservation id. 
Based on the reservation type, multiple arguments might be important. For example, for tensix reservations we would like to have starting point and grid size, for dram banks, ....
2. Release reservation: reservation id => (no return value, reservation is released) 
3. List all reservations: ReservationType => List of all reservations```

Issue with more details on the design in https://github.com/tenstorrent/tt-kmd -> TODO: add issue in KMD

[broskoTT]