1510 add reconstructed ephemeris to kernels that trigger only new coverage

[tmplummer]

Extend reconstructed-ephemeris coverage narrowing to new-coverage-only triggers

Context

Builds on the prior "reconstructed SPICE coverage triggers" work in this branch — this rounds it out by (a) actuareconstructed as a growing kernel type, (b) suppressing triggers from predicted kernels, and (c) restoring thepointing_attitude event emission that predicted-kernel filtering had inadvertently dropped.

Summary

• Add ephemeris_reconstructed to GROWING_KERNEL_TYPES in spice.py so newly ingested reconstructed ephemeris kernels only trigger reprocessing for genuinely new coverage (via the existing append/version-bump/rollover logic), instead of re-triggering already-processed time ranges.
• Add a NON_TRIGGERING_KERNEL_TYPES set (attitude_predict, ephemeris_predict, ephemeris_predicted) and check it i.py) so predicted kernels are skipped entirely during trigger evaluation rather than causing reprocessing —predicted data is superseded by reconstructed data and shouldn't drive partition triggers. Note the dual naming (ephemeris_predicted in dependency YAML vs. ephemeris_predict in indexed SPICE metadata) is guarded against explicitly.
• Add pointing_attitude back to the list of kernel types that emit SPICE events in spice_indexer.py (send_spice_eped and would have prevented downstream triggering for that kernel type entirely.
• Minor robustness fix in _parse_interval_list to accept intervals that are already datetime objects, not just ISO strings.

Tests

• New tests/lambda_endpoints/test_spice_dependency_triggers.py covering:
  • ephemeris_reconstructed kernels only triggering partitions for new coverage (not previously-covered ranges).
  • Predicted ephemeris kernels producing no triggered partitions at all.
• Extended test_spice_indexer_lambda.py with test_send_spice_event_filters_kernel_types to verify events are stiltory, pointing_attitude, ephemeris_reconstructed, attitude_predict, and ephemeris_predict.

Closes: #1510