explore possibilities to handle an object both as FLUXSTD and SCIENCE

Some of the FLUXSTDs from run21-23 were duplicated with SCIENCE targets from open-use programs. Because we gave a higher priority to FLUXSTD in the fiber assignments, the duplicated objects were observed as FLUXSTD, not as SCIENCE. As a result, they were coadded as FLUXSTD and the PIs could not see their objects in their pfsCoadd files. SAC expressed a concern about this, although they understand the importance of the calibration objects.

This ticket is to explore options to deal with such a case at the pipeline level.