Fix workflow to use correct FiveM artifacts API and document version tag persistence

[Copilot]

The workflow was using a non-existent API endpoint and lacked documentation on Docker tag behavior over time.

API Integration Fixed

• Endpoint corrected: artifacts.jgscripts.com/json (JSON API) replaces broken HTML scraping attempt
• Data extraction: Parses recommendedArtifact and linuxDownloadLink from JSON response
• Version parsing: Extracts full version string (e.g., 24574-315823736cfbc085104ca0d32779311cd2f1a5a8) from download URL via regex

# Build matrix now creates both tags from single recommended artifact
Matrix: {"artifact":"24574", "fullver":"24574-...", "tag":"latest"}
Build:  -t IMAGE:latest -t IMAGE:24574

Tag Persistence Documented

Version-specific tags (e.g., 24574, 24580) are permanent and never overwritten. Only latest updates on each build.

Timeline example:

Week 1:  [latest→24574] [24574]
Week 3:  [latest→24580] [24574] [24580]  # 24574 persists
Week 5:  [latest→24586] [24574] [24580] [24586]  # all persist

Best Practices Added

• Production: Pin to specific versions (image: ghcr.io/skriptzip/docker_fivem:24574)
• Development: Use latest for automatic updates
• Upgrade process: Test new versions before updating pinned version number
• Rollback: Simply revert to previous version tag

Enables predictable deployments, easy rollbacks, and version testing without breaking production.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.