Design a mechanism to store the output from shuffle in opDB

Currently opDB has no table for the output from `ets_shuffle`, so come up with a mechanism in opDB to store the information of the selected guide/acquisition stars in each camera.

Currently, the output of the shuffle processing is like this but we may have more information:
Identified target IDs for each camera: AG camera #0 [2493596405047282176 2493597813796555648] AG camera #1 [2492943913615230592 2492943913615227776 2492991020816540672] AG camera #2 [2492877221363219712] AG camera #3 [2493142272384857344 2493142448479083136 2493142169305639680 2493142585918005120] AG camera #4 [2494051431062162944 2494051057400740608 2494047999384032512 2494050988681269248 2494051362342685056 2494050984385562752] AG camera #5 [2493685637288060288 2493685469784142336 2493685469784142592
2493690177068271488 2493690172773592832]