Add interval and expires_in support to Device Code Flow

[Copilot]

The OAuth 2.0 Device Authorization Grant response includes interval (minimum polling interval) and expires_in (device code lifetime) fields that were being ignored, causing hardcoded 5-second polling and no timeout handling.

Changes

Backend (D4PDeviceAuthHelper.codeunit.al)

• Extract interval and expires_in from device code response
• Validate values are positive; default to 5s and 900s respectively
• Return values via new output parameters on RequestDeviceCode

Frontend (D4PBulkLoginControl)

• Accept interval/expires_in parameters in StartLoginProcess
• Use server-specified interval instead of hardcoded 5000ms
• Add timeout that stops polling and notifies user when device code expires

Example flow

// Before: hardcoded 5s polling, no timeout
setInterval(poll, 5000);

// After: server-specified interval with timeout
var intervalMs = (intervalSeconds || 5) * 1000;
setInterval(poll, intervalMs);
setTimeout(handleExpiry, expiresInSeconds * 1000);

---

💡 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.