[Feature Request] Optional loading of `raw_data` attribute about beep HOT 1 CLOSED

So after examining this a bit, it seems the breakdown is this:

• Reading the data file into a dictionary: 58% of the time
• Creating the Datapath object (from_dict): 42% of the time

By simply not adding in the raw data to the object, we can reduce the "Creating the Datapath object" by about 78%, AKA reducing the total load time by 31%. Source: loading the structured big test file (250MB) on laptop repeatedly

This simple fix might also take care of the memory issues.

I'm not sure the best way to programmatically not load the raw file from disk into dictionary; one way around it would be changing the defaults so that raw data is not saved unless specified, then the current BEEPDatapath code would automatically ignore the data and the run would be marked as "legacy". I'll update my PR with some timing results.

Edit:

Decided to just not save raw data when using CLI by default. It's the easiest and cleanest solution, requiring no changes to as/from_dict. See #250

from beep.