Remove dktk and bbmri feature flags

[timakro]

• Project is now selected via project metadata field
• SQL feature is enabled by default
• We only build one image samply/focus:main (previously we had samply/focus:main-dktk, samply/focus:main-bbmri)

[enola-dkfz]

Get a green light from @lablans, features are his babies

[Threated]

So previously this was just decided on the feature flag right?
So unknown projects that talked to a dktk focus would have gotten dktk semantics and did not get rejected?
So this, as is, is definitely a breaking change since there are a lot more "projects" that talk to the dktk focus like exliquid and dktk_supervisors (test lens). But I guess adding these is just a matter of adding enum variants and fixing compile errors.

[timakro]

So this, as is, is definitely a breaking change since there are a lot more "projects" that talk to the dktk focus like exliquid and dktk_supervisors (test lens).

The enum is only parsed if it is an AST query and many projects (e.g. exliquid) don't send AST. Maybe there are other projects than DKTK that want DKTK's AST->CQL semantics, we could add them to the enum.

Another breaking change is that some projects might not send the project metadata field at all right now. Would need to add PROJECT env var to their spot config.

[Threated]

r=me for the code. But we should figure out which projects we might need to add before merging this

[Threated]

Totally fine with merging this to develop but we need to check that all projects using AST have the project metadata configured correctly.