Remove FAP requirements for medium-latency circulars
Currently we have limits on whether we should include certain PyGRB and X-pipeline in medium latency circulars:
This could lead to an issue where we wish to create a circular for an event that has a FAP just beyond the boundaries set. In general ligo-followup-advocate should not make decisions on what is displayed to the public but only check what other pipelines have already chosen.
A solution for this is to give a keyword argument and also check that the appropriate files are present instead.