Add error handling for encrypted oJob file parsing failures

[Copilot]

When dbIP() decryption fails, it returns raw bytes as a string. This fallback was then parsed as YAML/JSON without error handling, producing cryptic parser errors instead of actionable messages about decryption failures.

Changes

• Wrapped parsing in try-catch blocks for fnReadEncYAML, fnReadEncJSON, fnDownEncYAML, fnDownEncJSON
• Replaced silent error swallowing in fnDownEncJSON with explicit error messages
• Added descriptive error messages that indicate the file/URL, suggest decryption key issues, and include underlying parse errors

Example

Before:

// Silent failure or cryptic YAML/JSON parse error
var _r = JSON.parse(content);  // Fails with "Unexpected token" on raw bytes

After:

try {
    _r = JSON.parse(content);
} catch (e) {
    throw "Failed to parse encrypted JSON file 'config.json.enc'. The file may not be properly encrypted or the decryption key may be incorrect. Error: " + e.message;
}

---

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