DOC: Example of data output for archival

[jklenzing]

Description

Addresses #6

Includes basic examples in the docs and links to the ops_reach project for people who want to build archivable data products.

Type of change

• This change requires a documentation update

How Has This Been Tested?

Inspection at the docs: https://pysatnasa.readthedocs.io/en/doc-6_example/archival.html

Checklist:

• Make sure you are merging into the develop (not main) branch
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• Add a note to CHANGELOG.md, summarizing the changes
• Update zenodo.json file for new code contributors

If this is a release PR, replace the first item of the above checklist with the release
checklist on the wiki: https://github.com/pysat/pysat/wiki/Checklist-for-Release

[jklenzing]

@t-esman, if you've run into other things while working on ops_maven, this would be a good place to document.