Editor: Rewrite reordering function to avoid over-aggressive touching of neighbouring records
This problem is only apparent in the info record tables, because that is the only place where we support record reordering right now.
Currently when a record is moved all neighbouring records are set to modified state and have the next/prev fields adjusted. Instead we should avoid modifying neighbouring records in base state. The next/prev information of the modified record itself should be enough to maintain the correct order, since these will always be loaded after the base record.