Re-think /data/ directory structure

[mvkovatch3]

The current data folder layout leaves something to be desired.

Ideas for improvement:

• [ ] logs is currently a dumping ground for too many things
  • [ ] move fitting_figs from logs up to data
  • [ ] qual flags?
  • [ ] do fitting coefs belong here? or in respective parameter folders? (reftmp, etc.)
• [ ] flags folder? or should flags go in respective parameter folders? (reftmp, etc.)
• [x] ditch scratch_folder?
• [ ] data inbox and outbox (potentially related to ctdcal import ___ idea)
• [ ] move converted, time, and bottle down a level? users shouldn't really interact with those files

The overarching point is to make it easier and more sensible for users to navigate.

[Klankers]

Discussed with @asmith75218 today. Looking at the following:

• CTDCAL folder - conssiting of all core code that shouldn't be modified
• Inbox folder - consisting of raw and discrete files that will (ideally) not be changed
• Outbox folder - consisting of all CTDCAL data products, logs, figures, reports, and statistics
• User/settings/"changes" folder - consisting of files the user changes to alter how the run is done (such as ssscc lists, run settings, cruise configuration, etc.)