Track options

[shaunlebron]

For example:

• ns has what could be considered options
• compiler options
• repl options

[shaunlebron]

I think it makes sense to have entries for each compiler and repl option since they are often referred to by functions and vars that use them. I don't think this is the case for ns options, and it is easy to determine where to find them since they are under the ns form and thus ns api entry.

[shaunlebron]

Used Figwheel's compiler option docs as reference:
https://github.com/bhauman/lein-figwheel/blob/master/sidecar/src/figwheel_sidecar/schemas/cljs_options.clj

[shaunlebron]

There are some options for which source functions could be included to clarify the usage and implementation.

• source-map-asset-path in emit-source-map

[shaunlebron]

examples of options we can make:

• ns/require
  • require/refer
• ns/require-macros
  • require-macros/refer
• foreign-libs/file-min
• destructure-vector/as
• destructure-map/keys

I think it is okay to leave the markdown files for these minor options empty, and just use them for tracking when they're added, allowing a better search index, and allowing URLs to where they are documented (as anchor links to where they are mentioned in their parent's page)