Improve performance of search by ID (num)

[dericcain]

In order to gain better performance when searching by ID, we are creating a lookup table that contains the num->name when the component is instantiated. If an ID is used to search, then we reference our lookup table and return the results. This should be a really fast solution since we are performing all of the efforts up front.

Closes #20

By submitting this pull request I confirm I've read and complied with the below declarations.

• [x] I have tested the changes locally and they are functional.
• [x] I ensure that my commit message is in imperative manner.
• [x] I ensure that I have properly referenced the related issue.
• [ ] I ensure that I sent this pull request after being assigned to the corresponding issue.
• [x] This pull request has a descriptive title. For example, Add/Fix {Feature/Bug}, not Update README.md or Add new code.
• [x] This pull request will be closed if I fail to update it even once in a continuous time span of 7 days.

[anshumanv]

Hey @dericgw really thanks for this! Can you please resolve the merge conflicts? :smile:

[dericcain]

@anshumanv I ended up having to completely refactor the "Search" because all of the logic that once lived in the component was moved to the helpers file. Now, you have a nice, clean search class that handles everything pertaining to search. And, the lookup speeds things up when searching by ID.

It looks like a test was broken in a previous commit which was merged without a PR (that is why there are no other failed CI tests). I would imagine that this happened when react-autocomplete was introduced because that specific test is looking for a direct child as an input an react-autocomplete seems to wrap the input in a div.