Scrape Vendor APIs for Available Numbers

[uncheckederror]

@danry25 Right now the limitation on speed is due to the latency of the TeleAPI that this application is dependent on.

Ideally we would scrape all of the data required for this app once a day from the TeleAPI and then cache it in a database like SQLite or PostgreSQL so that we can control performance.

Originally posted by @uncheckederror in #7 (comment)

[uncheckederror]

Per our internal discussion the plan is to spin up a copy of PostgreSQL and then write a console application that bulk scrapes these APIs and loads the data into a table. At which point NumberSearch will be refactored to reduce the scope of it's responsibilities. Rather than directly querying these vendor APIs it will instead query against this ingest table to look up available phone numbers. When a phone number is selected NumberSearch will directly query the API that provided that phone number to capture its current state and verify its continued availability, then it will bump to a form to collect the customer's information, and finally wrap that all up into an email that is sent by the application to the customer's email and the order fulfillment email.

[uncheckederror]

To support this goal we should do this work items:

• Break the data models out into a dotnet standard 2.1 library called NumberSearch.DataAccess to be shared between multiple projects.
• Create a console app called NumberSearch.Ingest that can be run daily to ingest data into PostgreSQL.
• Integrate a mail client into NumberSearch.Mvc that can handle the order creation process.

[uncheckederror]

This is complete as of commit c421efc