Remove silent fallback in dbIP to surface decryption failures

[Copilot]

The dbIP method was catching decryption exceptions and silently returning raw bytes as a string, making it impossible to distinguish successful decryption from failure. This masked errors until downstream YAML/JSON parsing, producing confusing error messages.

Changes

• Removed try-catch wrapper that converted decryption failures into silent fallbacks
• Added throws Exception to method signature to propagate decryption errors
• Exception handling already exists in calling code (js/owrap.oJob.js's _load function)

// Before: silent fallback on decryption failure
public String dbIP(Object aBytes) {
    // ...
    try {
        return AFBase.decryptBytes2String(aBytes, null);
    } catch (Exception e) {
        return new String((byte[]) aBytes);  // Masks the error
    }
}

// After: explicit failure propagation
public String dbIP(Object aBytes) throws Exception {
    // ...
    return AFBase.decryptBytes2String(aBytes, null);
}

Decryption failures now surface immediately with clear error context rather than manifesting as downstream parsing errors.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[nmaguiar]

Original behavior is intended "If decryption fails, return as string"