Review model module naming conventions

[BenSchZA]

Currently, the model modules are as follows:

• accounting.py
• ethereum.py
• proof_of_stake.py
• eip1559.py
• etc.

Consider refactoring if necessary to make these classifications more clear. Barnabe suggested finalization and justification as concepts worth considering: https://our.status.im/two-point-oh-justification-and-finalization/ . @rogervs suggested looking at the Eth2 spec. test suite to see what the architecture is.

Accessibility and value for learning should be prioritized, and sticking to the existing Eth2 spec and standard terminology.

[rogervs]

Suggestion for eip1559.py to become :

• gas_fee_management.py
• gas_management.py
• load_management.py
• transaction_load_feedback.py
• fee_management.py

[BenSchZA]

Thanks for the suggestions! @rogervs I've subsequently moved the EIP1559 logic into ethereum.py, and renamed it as policy_eip1559_transaction_pricing(...) so that it's familiar with people having read the economic report, and generally it's a topical upgrade at the moment. If people Google EIP1559 they will be able to see the specification of the mechanism. We could always give it a more generic name in a future update. In the spec they call it a "transaction pricing mechanism" which translates nicely to cadCAD logic naming.