Add "scripting tips" section to the documentation?

[glwagner]

Interacting with modeling software via scripts is novel for some users. We (and many others) are accumulating knowledge in this area, including:

• Scripting philosophy and its advantages.
• Literate scripting style for "paper-like" code, tutorials and pedagogical applications.
• Best practices for parameter exploration (eg how to replicate the functionality of a parameter file or namelist in your script, and why divorcing parameter lists from model setup should be considered carefully).
• Best practices for reproducibility (naming conventions, using output directories, checkpointing, script reuse).
• The use of external packages to achieve these goals (like ArgParse, or perhaps DrWatson).

Oceananigans tries to give users great power and flexibility for designing numerical experiments. However, with this power comes great responsibility for users to write and use their scripts for Good. We can possibly help by adding some documentation. I also think the writers of said documentation might benefit if said documentation stimulates community input / outside contributions to these best practices.

cc @ali-ramadhan @navidcy @kpamnany @kburns

[glwagner]

Closing this; let's keep track on #1852