Evaluate TOM workflow for an ANTARES filter

[rachel3834]

ANTARES is one of the main alert brokers for Rubin. It offers a number of public alert filters and the option for users to upload their own filters.

The TOM Toolkit already supports a basic query of the ANTARES broker but this has not really been road-tested for in an active Rubin alert follow-up program.

The tasks here would be:

• Compose a trial query of the ANTARES broker using the existing TOM plugin.
• Review the functionality offered by the ANTARES API to evaluate what query functions would be desirable to add
• Document the workflow required for a TOM to automatically harvest alerts from a given ANTARES filter

[rachel3834]

Comparing the ANTARES UI with the TOM's form, it looks like the default TOM form exposes most of the features that I would like to see for a microlensing query. The one major thing that is missing is an option to search on catalog, but unfortuantely
from the ANTARES client API documentation it seems that they don't offer an API that could populate the available catalog options for this field.

The main use-cases for MOP querying ANTARES are:

• Recent alerts that passed the microlensing filter. This filter will be run at the ANTARES end and will annotate alerts that pass with a tag. The existing form offers the capability to do this query using an MJD date range. A convenience function would be to have a button that allows queries within the last 24hrs.
• Search on locus ID that isn't a ZTF ID - currently the ANTARES client supports queries by locus ID as well as ZTF ID. This would enable users to search more generally.

UI updates specific to MOP:

• Update the template to support the dark-mode MOP layout and navbar, and change the colors of the headers.

Other features that would be generally beneficial:

• Search on GW event ID

[rachel3834]

Once microlensing tags are available in ANTARES, we will want to create a management command to call the TOM's ANTARES broker class with a dictionary of parameters along the lines of:

search_params = {
  'tag': <microlensing tag>,
  'mjd__gt': <float>,
  'mjd__lt': <float>
}

then call the broker class's to_target method to create targets in the TOM.

This automatically handles the duplication checking.

[rachel3834]

One outstanding feature that still needs to be added to the ANTARES Broker is to automatically ingest the photometry data for a new target.

For some users, ingesting the image triplets would be useful as well. This is not required for MOP and brings with it questions of which of the triplets (all?) should be ingested; potentially a big-ish query. This can be left for another time.

[rachel3834]

This PR to the tom_antares module should fix the form UI issue and allow MOP's custom CSS to override the template properly.

The same PR also provides the functionality to more easily search for alerts from the last 24hrs and to search on locus ID as well as ZTF ID.

For the record, although GW GraceDB ID can be associated with loci, the ability to query on these IDs does not seem to be exposed yet in the ANTARES client library, so this was not easy to add.