FEAT: Enable Algolia integration

[sumitsarkar]

1. Integrating with Algolia API (via POST). GET is unimplemented as its usage is discouraged.
2. Supports pagination.
3. Doesn't support explain, highlight, snippet and ability to retrieve document via id.

Closes #144

[epugh]

This is looking really great! Thanks for writing some detailed tests. There is definitly some refactoring as we add more search engines that could be done in seperate PR's. I have a couple of comments...

[epugh]

@sumitsarkar are you planning on doing the work in Quepid as well? I'd love to have you pick up that side as well, and then when the PR for Quepid is done, we merge both of these at the same time, I bump this splainer-search, bump it in Quepid, and then cut a release? I guess I don't know how comfortable you are modifying Quepid... Basically search for the word "vectara" to find all the places that need changing!

[epugh]

LGTM, pending figuring out if we ship it now, or first get the Quepid integration working (in case we need to modify this some more), and then ship it...

[sumitsarkar]

LGTM, pending figuring out if we ship it now, or first get the Quepid integration working (in case we need to modify this some more), and then ship it...

I'd be in favor of preparing a Quepid integration working first. I have a working version already. Will clean that up and prepare a PR.

[epugh]

does the /1/ imply there is a /2/?? or will it alwyas be like this?

[sumitsarkar]

It is the API version number. It could change in the future. But it's unlikely the version will be deprecated and removed quickly. There should be time for migration to new API version number.
Source

[epugh]

working through another PR, and then hope to get this in first thing this week... once I have tested with my demo algolia account!