Hack-ey way to make sure materials are tracked

[abachma2]

Expected behavior:

• call ts.Material.create_untracked() in the get_material_requests function
• The discharged material from the archetype and and subsequent materials from that one are tracked in a simulation

Current behavior:

• call ts.Material.create() in the get_material_requests function
• The discharged material from the archetype and and subsequent materials from that one are tracked in a simulation

When ts.Material.create_untracked() was previously called, the discharged material from this archetype and any subsequent materials were not tracked as resources (although the transactions were recorded). This problem was previously addressed through Issue #9, with an attempted by wrong solution implemented in PR #15 (this solution recorded information to the database without actually making the materials tracked). The current behavior seems to work well enough (although it does add a lot of resources to the database), but it feels like something that the archetype shouldn't be doing.