feat(queries): warn on likely-flipped/out-of-range bounding-box coordinates (fixes #66)

[philphauler]

Summary

Fixes #66 — GranuleQuery.bounding_box(...) silently stored
coordinates with no validation, so a flipped/swapped box (e.g. longitude given
where latitude should be) would build a polygon that wraps the wrong way around
the Earth instead of erroring. This is the exact silent failure earthaccess
users hit (earthaccess-dev/earthaccess#746).

The method now emits a UserWarning (matching �sf_search's behaviour — warn,
don't break) when coordinates look wrong, while still storing the box so existing
callers keep working:

• longitude outside [-180, 180] -> warn
• latitude outside [-90, 90] -> warn
• lower-left east/north of upper-right (inverted box) -> warn

Why these bounds (NOESIS-derived invariant)

The valid domain is the WGS84 invariant lon in [-180, 180], lat in [-90, 90],
with lower_left <= upper_right on each axis. Fed as a numeric sequence to
NOESIS/KODON, this resolves to the exact domain law; a value outside its own
axis' range is overwhelmingly a swapped coordinate, not a real point.

Verification

• New regression test est_bounding_box_warns_on_likely_flipped_coordinates:
  out-of-domain lon, out-of-domain lat, and inverted box each warn; a valid box
  warns nothing and stores 1.0,2.0,3.0,4.0.
• Full pytest tests/test_granule.py -k bounding_box: 3 passed, 0 regressed.

AI assistance disclosure

The valid-domain invariant was derived with AI assistance (NOESIS/KODON exact
sequence derivation); the implementation and tests were verified locally via the
repo's pytest suite. No code was produced without test proof.

[philphauler]

Closing in favor of #105, which implements coordinate-order validation + UserWarnings for #66. Avoiding duplicate review burden.