543 add current year lfps support to api for landfire fuel models

[lindsaywiard]

The API now accepts the latest year's release for FCCS, FBFM13, and FBFM40 through version, gated by a live LFPS coverage check before the grid is created.

Changes

• services/api/api/resources/grids/{fbfm13,fccs,fbfm40}/schema.py

  • Widen the version enum to include the current lfps_available year
  • fbfm40's check_version_matches_season validator is simplified
  • Update each version field's description to name the current LFPS-sourced year

• services/api/api/resources/grids/{fbfm13,fccs,fbfm40}/router.py

  • Call validate_lfps_coverage before creating the grid whenever the requested version is lfps_available
  • fbfm40's existing season-only gate is widened to also cover the no-season "latest release" case

• services/api/api/resources/grids/{fbfm13,fccs,fbfm40}/examples.py

  • Add a latest_release documented example for each product.
  • Split each product's example list into STAGED_*_EXAMPLE_VALUES (staged data, tested against any domain) and LFPS_*_EXAMPLE_VALUES (LFPS-sourced, tested against a domain with known coverage).

• services/api/tests/resources/grids/{fbfm13,fccs,fbfm40}/test_schema.py

  • Add a test confirming the lfps_available version is accepted.
  • fbfm40: removetest that asserted an lfps_available version with no season was rejected

• services/api/tests/resources/grids/{fbfm13,fccs,fbfm40}/test_router.py

  • Add a TestLfpsCoverage class with a real, live-coverage test of the latest_release example against lfps_covered_domain — confirms validate_lfps_coverage actually succeeds against LFPS

[amarcozzi]

Looks good thank you! I left a comment about expanding the example descriptions but I'll leave it up to you if you want to address those or go ahead and merge.