Lock fields to prevent changes through directus

Summary When having fields managed from outside of directus (e.g via code in migrations or external systems) sometimes it's useful to prevent users from making any changes from those fields. This makes sure that the code configuration is the single source of truth. On non-special fields it's possible by 'missusing' the 'systems' field attribute to at least prevent changes from the admin app: For special fields (aliases, groups, etc) this is not possible, as their data are parsed different. Basic Example _No response_ Motivation Prevent admins from modifiying single fields / tables that are managed by third party or via code. Detailed Design In directus fields there could be a new column 'locked'. The logic to protect the field could be reused from the 'system' check that already exists. Requirements List Must Have: • Config to protect field • Disable changes in UI • Disable changes from API …