Give some flexibility on Directus users interface

Summary The directus_users' interface is rich but rigid. I never encountered 2 organizations that want the same interface. Hence, on every project, I have to build a one to one table that offers the wanted interface and maintain the 1-1 link with triggers (not ideal) or have only an API use of the table. Basic Example _No response_ Motivation Fit the client requirements Detailed Design For instance, location and other fields like tfa_secret, token, etc. should bi unlocked so we can, i a role, not allow not to show them. Also the fixed order is not the one suited in most cases. Requirements List Must Have: • A • B Should Have: • C Could Have: • D Won't Have: • E Drawbacks A minimal list of necessary fields should be kept : email, role and password. (First name and Last name are not on the required list as they don't apply to a "user" who is an organization) Alternatives Build one's Form and con…