Refresh examples

[plicease]

Big Example Refresh PR

This is for #383 but we will also hopefully touch on other documentation PRs as we work on this.

Order

• [x] The examples should be reordered from least to most complicated, finishing with a full dist example. Some of the examples are already appropriately placed, but some are totally wrong.
• [x] Integer example
• [x] String argument example
• [x] String return example (possibly more than one, owned, unowned, static, etc)
• [x] Pointers
• [x] Opaque (objects)
• [x] Opaques (malloc/free, buffers, strdup)
• [x] Arrays
• [x] Pointers as arrays
• [x] Unix GUI (libnotify)
• [x] Windows GUI (MessageBoxW)
• [x] FFI::C
• [x] Record
• [x] Buffers (FFI::Platypus::Buffer)
• [x] Window (FFI::Platypus::Buffer::window)
• [x] OO opaque (libarchive)
• [x] OO integer (unix open)
• [x] variadic functions (libcurl)
• [x] Callback
• [x] Bundle code

Format

• [x] New format: each example should include these sections (some are optional):

  1. C API (for external libraries) this can be a link to the appropriate documentation
  2. C Source (for bundled examples)
  3. Perl Source
  4. Execute
  5. Discussion

Pictures

• [x] GUI stuff should have images in the HTML. This should live in the Execute section. In think there are only two examples so far:
• [x] libnotify
• [x] MessageBoxW

Rework stuff removed in these refactors

• [x] Using FFI::CheckLib to find libraries
• [x] Renaming functions when attaching
• [x] use of function vs. attach (this should maybe go into the varadic / curl example)
• [x] using wrappers

Testing

• [x] examples should be easily tested
• [x] using prove
• [x] and CI
• [x] examples that cannot easily be tested in at least CI should be removed (possibly exception: GUI examples)