Initial setup for challenge submission route

[MattPereira]

Closes #2 Closes #4 Closes #5

Follow the updated README.md instructions to review this PR

Overview

• install.ts script to fetch, save, and update the challenge repositories
• Temporary GET route for challenge submission that will eventually be refactored into a POST
• Validate the params for the submission route with express-validator
• Use submitted address and networkto fetch the contract source code from Etherscan and save it into the appropriate challenge repo
• Execute forge test from within the challenge repo ( does not currently target the downloaded contract )

Future Issues

• 8

• 9

• 10

[MattPereira]

@escottalexander the scripts have been amended to install all the challenges into a challenges/ directory. I also figured out how to speed up the submission route results by adding forge install to the install.ts script so that we don't have to wait for foundry submodule installs the first time the route is consumed.

Let me know what you decide about axios and express-validator and if the changes should be made as part of this PR or future PR

I kinda think it makes sense to stop here with this PR so you can play with the flow of operations as you decide what kind of response you want to send back to your CLI client and determine what fields you want to keep track of in the database