Simulation grouping

[jorekart]

I think it would be useful to have simulation groups when ingesting a simulation, for example after "simdb simulation list" one could have

• group1/sim1
• group2/sim1
• group2/sim2

And one could delete, validate or push directly a simulation group (e.g. :"simdb simulation push group2"). Maybe the easiest would be to add a metadata field in the manifest file defining the group membership.

[olivhoenen]

Two aspects here:

• using a notion of groups for queries --> this can already be done by an ad-hoc construction of aliases
• ingesting and pushing batches of related simulations (e.g. from a parametric scan)

Now in principle batch operations could also be concerning simulations that have not always close relationship (think git push that may contain several unrelated commits, but in case of simdb things are a bit more complicated because the simulations in the local DB may not all be pushed to the same remote).