feat: create a carrier class for each carrier #60
Description
Description, issue
Currently...
- carrier formatting is a mess (when to use short-hand ("CH") vs longhand ("Chubb"), lower-case vs. upper-case vs. sentence-case;
- carrier objects are currently defined as dicts in more than one spot;
- code duplication is most prevalent because of this issue
- no current method exists to even represent a carrier as a string, which would be more convenient at times.
Solution
- create carrier.py that will be responsible for generating carriers as objects, with all real-world properties---that may require fixing/updaing/maintaining in the future due to real world changes---defined in one area;
- clearly define all properties of the carriers;
- pass the carrier object to the config-worker and presenter;
- re-examine to see which methods can be stored internally within the carrier objects;
Alternatives
Dicts carrying varying data around, which could be improved with NamedTuples, which then can be improved by just using another class object to also have accompanying methods for more extensibility/convenience.