Fix scans being registered twice in Command::Run

[SethDusek]

Hi, relatively minor issue I ran into while testing, but I noticed that scans for each type (pool/ballot/refresh/etc) were being registered twice when I ran oracle-core run for the first time (with scanIds.json removed). After testing it with other commands that also create a new OraclePool that were not having this issue, it seems the cause was that the HTTP Get API thread and the main thread in Command::Run were both running in parallel and registering scans twice.

[coveralls]

Pull Request Test Coverage Report for Build 2846619236

• 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage remained the same at 65.163%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
core/src/main.rs	0	1	0.0%

Files with Coverage Reduction	New Missed Lines	%
core/src/main.rs	1	0%

Totals
Change from base Build 2838643233:	0.0%
Covered Lines:	1964
Relevant Lines:	3014

---

💛 - Coveralls

[greenhat]

Great catch! Thank you!
I think we should have only one instance. I made #97