Make ID field a UUID / replace by sodar_uuid

[holtgrewe]

Problem

All sodar-core based apps inherit the expected behaviour that id is a plain integer primary key while sodar_uuid is a UUID. The sodar_uuid is used for everything facing the outside world, in particular URLs and REST APIs. This behaviour works well for internal code but for code such as drf-writable-nested this is problematic.

Solution

Create migrations for the models that:

• adjust foreign key columns to point to the sodar_uuid
• drop the integer primary key column
• rename sodar_uuid to the primary key column name

This is a huge change and should not be considered before a 2.0 version.

Alternative Solutions

N/A

Additional Context

• https://github.com/beda-software/drf-writable-nested