feat(integration-platform): remove code-based jumpcloud, route via DIP

Code-based jumpcloud manifest blocked the DIP (din_69b976d08043fc0becee137d)
from running. DIP version has the device posture checks customers need for
SOC 2 / PCI evidence — disk encryption (fde.active), OS version, OS patching
via System Insights — which the code-based version did not.

Removed:
- packages/integration-platform/src/manifests/jumpcloud/ (entire folder)
- 2 lines in packages/integration-platform/src/registry/index.ts (import + array entry)

After deploy, registerDynamic() will accept the DIP version and customers
get 4 checks (user_access, mfa_enrollment, systems, os_patching) + sync.

Existing JumpCloud connections keep working — credentials are stored by
connectionId in the vault, manifest auth-type is read from the manifest
(not the connection record), and DIP code steps explicitly inject
x-api-key headers. No reconnect needed.

Note: Employee sync still routes through the dedicated
sync.controller.ts @post('jumpcloud/employees') path via
sync-employees-schedule.ts case 'jumpcloud' — that pipeline is untouched.
DIP syncDefinition is built but inert until the dedicated path is also
removed (separate PR).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: tofikwest