Description of problem:
In the steps to use OLM on a restricted network the documentation directs to use the now deprecated Pruning a SQLite-based index image approach. Is there a non-deprecated method that can be used when pruning the operator-index? If so this should be used instead in the 4.9 docs.

Version-Release number of selected component (if applicable):
4.9

Location in docs:
https://docs.openshift.com/container-platform/4.9/operators/admin/olm-restricted-networks.html#olm-pruning-index-image_olm-restricted-networks

Steps to Reproduce:
1. Run podman run -p50051:50051 -it registry.redhat.io/redhat/redhat-operator-index:v4.9

Actual results:
podman run -p50051:50051 -it registry.redhat.io/redhat/redhat-operator-index:v4.9
WARN[0000] DEPRECATION NOTICE:
Sqlite-based catalogs and their related subcommands are deprecated. Support for
them will be removed in a future release. Please migrate your catalog workflows
to the new file-based catalog format.

Additional info:
Pruning a SQLite-based index image is listed in the 4.9 deprecated notes.
https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.html#ocp-4-9-deprecated-removed-features