Add an OCI skill for complete paginated Logging Search exports

Summary

The OCI domain currently has no dedicated skill for exporting complete high-volume OCI Logging Search results. A single oci logging-search search-logs request returns one page and can appear capped, while OCI exposes continuation through opc-next-page and the CLI --page option.

Proposed skill

Add oci/logging/oci-export-large-logs to:

• follow every page token without changing the search query or UTC bounds
• stream results to a temporary JSON file and atomically publish it only after successful completion
• preserve every raw result, including repeated data.logContent.id values
• report page count, record count, requested coverage, timestamps, and empty-result status
• remain schema-neutral and read-only across service, custom, audit, load-balancer, and VCN flow logs

Motivation

During validation against VCN flow logs, a 1,000-record response contained only 490 unique data.logContent.id values. Deduplicating solely by that field would silently discard valid events. A paginated prototype subsequently exported 1,387 records over two pages while preserving all results, even though only 521 IDs were unique.

Validation available

• automated coverage for multi-page traversal, repeated IDs, repeated page-token failure, malformed responses, atomic output, and empty results
• live two-page OCI Logging Search smoke test
• repository skill validation passes
• no tenancy-specific identifiers, production payloads, or page tokens are included in the proposed contribution

An implementation and OCI domain navigation updates are ready for a pull request if this addition is accepted.

References

• https://docs.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/logging-search/search-logs.html
• https://docs.oracle.com/en-us/iaas/Content/Logging/Concepts/searchinglogs.htm
• https://docs.oracle.com/en-us/iaas/Content/API/Concepts/usingapi.htm#nine