Bake developer experience into Directus

Directus is great and powerful, but I think there are a few rough corners with the developer experience. For example: • Data migration seems manual, because, unlike most migration libraries, where we write or generate migration scripts at each stage, Directus generate a new independent schema snapshot in yaml, and Directus will somehow manage to update the schema from the new snapshot. This leads to un-unified, or non-standardized approaches to migration from dev to prod. • Some important metadata, such as custom roles, or any change to theme, app name, and logo are not synced between environments. • Flows, which is a hot topic, does not have a clear way to go from dev to prod environment. All of these problems came from the fact that, in CD/CI, we share the code, and separate the data between environments. In Directus, however, we develop on data. I think that, to make Directus an ultimate headless CMS platform, we should consider the use case of a dev envi…