chore: make public api consistent

Summary:

Right now we have two ways to access the public api we have `require('ivy')`
and `vim.ivy. Each way has a different api that will cause some confusion.

Now both apis are the same so anyone that wants to integrate with ivy can do so
without having to figure out what one they need to use.

Test Plan:

The unit tests cover most of the work, I have also been using this locally for
quite some time now with now issues.

README.md

@@ -21,7 +21,6 @@ git clone https://github.com/AdeAttwood/ivy.nvim ~/.config/nvim/pack/bundle/star
 ### Plugin managers
 
 Using [lazy.nvim](https://github.com/folke/lazy.nvim)
-
 ```lua
 {
     "AdeAttwood/ivy.nvim",
@@ -29,31 +28,6 @@ Using [lazy.nvim](https://github.com/folke/lazy.nvim)
 },
 ```
 
-Using [mini.deps](https://github.com/echasnovski/mini.deps)
-
-```lua
-local deps = require "mini.deps"
-deps.later(function() -- Or `deps.now` if you want this to be loaded immediately
-  local build = function(args)
-    local obj = vim
-      .system(
-        { "cargo", "build", "--release", string.format("%s%s%s", "--manifest-path=", args.path, "/Cargo.toml") },
-        { text = true }
-      )
-      :wait()
-    vim.print(vim.inspect(obj))
-  end
-
-  deps.add {
-    source = "AdeAttwood/ivy.nvim",
-    hooks = {
-      post_install = build,
-      post_checkout = build,
-    },
-  }
-end)
-```
-
 TODO: Add more plugin managers
 
 ### Setup / Configuration
@@ -62,19 +36,19 @@ Ivy can be configured with minimal config that will give you all the defaults
 provided by Ivy.
 
 ```lua
-require("ivy").setup()
+require('ivy').setup()
 ```
 
 With Ivy you can configure your own backends.
 
 ```lua
-require("ivy").setup {
+require('ivy').setup {
   backends = {
     -- A backend module that will be registered
     "ivy.backends.buffers",
     -- Using a table so you can configure a custom keymap overriding the
     -- default one.
-    { "ivy.backends.files", { keymap = "<C-p>" } },
+    { "ivy.backends.files", { keymap = "<C-p>" } }
   },
 }
 ```
@@ -85,7 +59,7 @@ function, this can be used to load backends before or after the setup function
 is called.
 
 ```lua
-require("ivy").register_backend "ivy.backends.files"
+require('ivy').register_backend("ivy.backends.files")
 ```
 
 ### Compiling
@@ -143,7 +117,7 @@ customized when you register it.
 Action can be run on selected candidates provide functionality
 
 | Action         | Key Map     | Description                                                                    |
-| ------------------- | --------- | ---------------------------------------------------------------- |
+| -------------- | ----------- | ------------------------------------------------------------------------------ |
 | Complete       | \<CR\>      |Run the completion function, usually this will be opening a file               |
 | Vertical Split | \<C-v\>     |Run the completion function in a new vertical split                            |
 | Split          | \<C-s\>     |Run the completion function in a new split                                     |
@@ -159,14 +133,10 @@ Add your own keymaps for an action by adding a `ftplugin/ivy.lua` file in your c
 Just add a simple keymap like this:
 
 ```lua
-vim.api.nvim_set_keymap(
+vim.api.nvim_set_keymap( "n", "<esc>", "<cmd>lua vim.ivy.destroy()<CR>", { noremap = true, silent = true, nowait = true })
-  "n",
-  "<esc>",
-  "<cmd>lua vim.ivy.destroy()<CR>",
-  { noremap = true, silent = true, nowait = true }
-)
 ```
 
+
 ## API
 
 ### ivy.run
@@ -220,9 +190,7 @@ vertical split action it will open the buffer in a new `vsplit`
     end,
     -- Action callback that will be called on the completion or checkpoint actions.
     -- The currently selected item is passed in as the result.
-    function(result)
+    function(result) vim.cmd("edit " .. result) end
-      vim.cmd("edit " .. result)
-    end
   )
 ```