Adding organization_feature_access table & functionality

[carere]

No description provided.

[Pascal-Delange]

Thanks !
I left you some comments in the PR body.
The two main points I have to add here:

• at a high level, the idea is that the front no longer stores the license key, instead calls this new endpoint on the backend that will: read feature accesses, merge them with the features available on the license (which the backend validates with our license server), and return the merged set of features to the frontend
• as a result, while the API return DTO should contain all the relevant features, we only need to specifically store in the DB at the org level, those that we want to set at the org level. That is: sanctions, test run (as of today). So you can simplify by reducing the nb of features we store.
• last point, for orgs we create internally, the API should accept a list of features to add when the org is created, so we should add this input in the org creation API DTO, and pass it over to the org creation repository (end customers who self-host are not expected to use this)