Add 7-second delay to MeshMapper API posts after ping transmission

[Copilot]

The MeshMapper API posts need to occur 7 seconds after pings are sent to allow time for message propagation through the mesh network before comparison data is recorded.

Changes

• Added MESHMAPPER_API_DELAY_MS constant (7000ms) to centralize timing configuration
• Wrapped postToMeshMapperAPI() call in setTimeout() to defer execution

// Before: Immediate API post
postToMeshMapperAPI(lat, lon);

// After: Delayed API post
setTimeout(() => {
  postToMeshMapperAPI(lat, lon);
}, MESHMAPPER_API_DELAY_MS);

The fire-and-forget async pattern is preserved—ping transmission remains non-blocking.

Original prompt

In regard to Add automatic MeshMapper API posting on every ping #6

I actually need to delay the API post 7 seconds after the ping goes out on the meshcore network.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.