Problem with assigning a core UI

[poppyseedDev]

For example, Assigned cores disappear from the UI. This is problematic for obvious reasons. But sometimes users may want to assign cores to tasks that are NOT theirs, yet is the ability to manipulate cores (splitting) after assignment possible? Or can a user "unassign" a core assigned to task?

There are also ways we can improve the UI on this page to show the time better rather than RegionIDs which are opaque to the user. We should AT LEAST have block numbers, but preferrably do things always based on date and time, ideally grabbing the user's timezone from their browser.

Also, the cores are sorted arbitrarily. We need proper groupings, AND in-group sorting that makes sense, not necessarily customizable by the user.

Note Once you take on this PR paste a comment with your hand -> ✋ so that people know that someone is working on this issue.

[poppyseedDev]

Create a note when you click on assign titled:

**INFO**
Provisional: The region will remain under your ownership. Allowing the assignment of the task/paraId to be altered. However you won't be able to renew the assignment. Good for testing.
Final: The region is removed; the assignment may be eligible for renewal only if the region hasn't been manipulated (hasn't been partitioned or interlaced).

When the assignment finishes have a button for the user to check his paraId assignment: https://test.lastic.xyz/paraId

[phillux]

@poppyseedDev resolved?

[potmarion]

✋