Enhance the ALeRCE broker to add LSST and solar system support via TAP

[talister]

Summary

Extends the ALeRCE DataService in tom_dataservices so it can search, create targets from, and ingest photometry for Rubin/LSST objects in addition to the existing ZTF support. LSST searches (and the classifier lists for both surveys) go through ALeRCE's TAP service via pyvo, because the REST API can't yet filter LSST objects by classifier, list LSST classifiers, or provide the MPC orbits needed for asteroids (see this response from Alejandra of ALeRCE in Rubin Community) ZTF searches and light curves for both surveys still use the REST API through alerce_client.

Implements #1665 and also fixes #1669

Changes

LSST searches

• New Survey (ZTF/LSST) and LSST Object Type (diaObject / ssObject) fields. LSST general queries are built as ADQL against alerce_tap.object (cone search, first/last detection MJD, ndet range).
• diaObject classifier searches join alerce_tap.probability (top-ranked class, minimum probability), and results show the class and probability. ssObject classifier searches raise a clear error, since ALeRCE assigns every known ssObject "asteroid" with probability 1.
• Object ID accepts a diaObjectId, an ssObjectId, or an MPC designation (e.g. 2010 WX64), which is resolved to an ssObjectId through alerce_tap.lsst_mpc_orbits.
• New advanced-form fields: Max. Results, Sort By, Sort Order (both surveys), and Max. Detection Time Span (LSST only, for finding new asteroid candidates among diaObjects). lastmjd can now be given as a lower bound only.
• Classifier fields for both surveys are always on the form, and a shared Alpine store shows the selected survey's set, so switching surveys no longer needs a resubmit. clean() drops classifier values from the non-selected survey.
• Classifier lists come from TAP and are cached per survey (ds_alerce_classifiers_{tid}).

Targets and photometry

• LSST photometry is ingested: difference-image flux in nJy is converted to AB magnitudes, bands 1–6 are mapped to ugrizy, and TAI is converted to UTC. Data is tagged Rubin/LSSTCam. Detections with non-positive flux are skipped.
• ssObject targets are created as non-sidereal targets from ALeRCE's copy of the MPC orbit. Missing orbital elements are derived from q, e and peri time, as in MPCExplorerDataService. If there is no orbit, or the lookup fails, the target falls back to sidereal with a logged warning.
• Asteroid targets get their MPC provisional designation, permanent number, name and secondary designations as aliases.
• Update data now resolves the ALeRCE object from the target's name and aliases: ZTF/LSST IDs directly, AT/SN names through TNS internal names (if TNS is configured), and MPC designations through lsst_mpc_orbits. Targets created by TNS or MPC Explorer can therefore pick up ALeRCE photometry.
• Results and created targets link to the ALeRCE Explorer (alerce.online / lsst.alerce.online).

Bug fixes

• ZTF object ID lookups returned the paginated wrapper instead of the object (regression from 6539f4e).
• An LSST ID with no match raised IndexError; it now returns no results.
• Creating any LSST target returned a 500 and saved it without photometry, because TAP returns integer oids and Target.name was left as an int in memory.
• Re-querying photometry with revised uncertainties raised an uncaught ValidationError (Alerce DataService can crash when re-querying photometry for a target #1669). Existing datums are now matched on the uniqueness-constraint fields only and left unchanged.
• TAP outages no longer 500 the search, target-creation or query-form pages; they surface as QueryServiceError messages or graceful fallbacks.
• TestMPCExplorerDataServiceCanary never assigned self.target_result, so it failed before reaching the live API. This bug predates the branch and is also on dev.

Dependencies and docs

• pyvo >=1.5,<2 is declared as a direct dependency. It was previously only pulled in through astroquery; the locked version (1.9.1) is unchanged.
• New docs page docs/data_services/alerce.rst covering ZTF vs LSST querying, diaObject/ssObject searches, asteroid aliases, flux-to-magnitude conversion, and alias-based matching.

Testing

• 101 tests in tom_dataservices/tests/data_services/test_alerce.py cover form building, query parameters, the REST and TAP paths, error handling, and target/datum creation. The ALeRCE and MPC suites pass locally.
• LSST classifier and ssObject paths were checked against the live ALeRCE TAP service.
• End to end in a downstream TOM (FOMO, tomtoolkit 3.1): an LSST search for 2010 WX64 found ssObject 21164706944660568, and creating a target from it gave:
  • a NON_SIDEREAL / MPC_MINOR_PLANET target with its orbit from lsst_mpc_orbits;
  • aliases 2010 WX64 and 728999;
  • 44 LSSTCam detections in g, r, i and z as AB magnitudes (matching ALeRCE's ndet of 44);
  • an ALeRCE Explorer link.
  • ZTF microlensing example from Markus (ZTF24aaiafkl) and ZTF SNe example (ZTF24aamlalc) from ALeRCE notebooks also tested out fine

Some code and some of this PR text generated with Claude robots, end-to-end user testing done with humans