Feature request: replication priority

**Use case**:
Data in the system have varying degrees of criticality.
Some data are very crytical, some - not (e.q. logs).
But after restart crate starts restoration and replication process in random order.
I want to replicate critical data first.

**Feature description**:
New property at table level:
`ALTER TABLE xxxx SET (restore.priority = 10);`
`ALTER TABLE yyyy SET (restore.priority = 20);`
When crate select tables to restore - it will take first tables with largest `restore.priority`.
In sample - crate will first start replicate\relocate\restore table `yyyy` finish it, and only then starts replicate/relocate/restore table `xxxx`

Alternativly it may be property at schema level with same logic.