Compatibility: support Oracle JET/OJET MVVC release builds (AMD/RequireJS)

Problem

Using @ofs-users/proxy.js in Oracle OJET MVVC release builds fails.

Observed with ojet build --release (or just build in release mode):

• Build attempts to resolve AMD path: web/js/@ofs-users/proxy.js
• Resolution fails with ENOENT

Context

• Current package is ESM-first ("type": "module", main: dist/ofs.es.js)
• Sample/plugin build pipeline is RequireJS/AMD-oriented
• Direct import currently breaks OJET release build flow

Additional Typings Gap

• Assistants params typings currently expose dateFrom
• dateTo is not exposed in the same assistants params interface

Requested Outcome

Make the library compatible with Oracle OJET MVVC release builds while preserving backward compatibility for existing plugins already using the library.

Acceptance Criteria

• ojet build --release succeeds when consuming this library in OJET MVVC context
• Packaging/import strategy works for AMD/RequireJS consumers (without breaking existing consumers)
• Existing plugin integrations keep working (backward compatibility)
• Assistants params typings include dateTo (alongside dateFrom) in a non-breaking way

Notes

Please evaluate options such as dual package output (ESM + AMD/UMD-compatible entry), conditional exports, and/or documented OJET-safe import path with backward compatibility guarantees.

Start by inspecting the package metadata, especially "type" and "main", the packaging/import setup, and the assistants params interface where dateFrom is exposed. Run ojet build --release in the OJET MVVC context to reproduce the AMD resolution failure. Done means the release build succeeds, existing plugin integrations remain compatible, and dateTo is added non-breakingly.