fix: consistent full-width layout for areas and geofences pages

[hokiepokedad2]

Summary

• Remove max-width: 800px from .areas-page in area-list.component.scss

The Areas page was constrained to 800px while My Geofences used full-width, creating an inconsistent map experience. Both pages now use full-width layout since maps benefit from wider viewport space.

Closes #107

Test plan

• Areas page map renders full-width
• My Geofences page map renders full-width (unchanged)
• Both pages look consistent when navigating between them
• Areas page content (method cards, chip list) still looks good at full width

[hokiepokedad2]

Code Review: PR #110

Verdict: APPROVED ✓

Summary

One-line fix — removes max-width: 800px from .areas-page in area-list.component.scss to make the Areas page full-width, matching the My Geofences page layout.

Category	Assessment
Correctness	The constraint was the sole cause of the inconsistency. Removing it makes both map pages full-width.
Risk	Very low. CSS-only change, no logic affected.
Regression	None — the method cards grid and chip list reflow naturally at wider widths.
Tests	461 frontend tests pass. No test changes needed (CSS-only). 560 backend tests pass.

Note

The method cards section uses grid-template-columns: 1fr 1fr which will stretch wider on large screens. If that looks too spread on ultrawide monitors, a max-width on just the method cards (not the whole page) could be added as a follow-up. Not a blocker.

No issues found.