This is a tracking epic for tasks/issues with our processes and documentation around internal feature flag usage. Any issues related to our documentation or our processes for using feature flags internally should be kept in here. ### Add differentiation to `development` feature flags  It seems there are FF that are "blocked" for various reasons: - The feature has security vulnerability (https://gitlab.com/gitlab-org/gitlab/-/issues/337288#note_860455533) but since it's behind the feature flag (disabled by default), it's not ptioritized to be fixed (even though customers can already use the feature!). - The feature flag requires preparation (e.g. communication to customers, blog post, doc etc.) work (e.g. https://gitlab.com/gitlab-org/gitlab/-/issues/233550), so we may need to introduce ways to identify/separate them from the `FAST_ROLLBACK` feature flags. Alternatively, we could introduce new feature flag types to differentiate between `development` feature flags.