Pull in the rest of the LFE macros for eunit

[oubiwann]

This is a proposal, for @rvirding's approval:

Some of the macros that wrap eunit (from the ltest project) are already in LFE-proper (here), yet these are only here in order to run the unit tests on the clj.lfe library; they could be used by everyone/any project, if we structured things a little differently. The idea of providing an eunit wrapper in LFE-proper isn't all that bad, considering eunit comes with Erlang/OTP and isn't a third-party library. Note that the eunit wrapper DSL has only one dependency: LFE itself (it doesn't even require rebar3).

Required tasks:

• [ ] Make the eunit LFE wrappers easily available for inclusion in any LFE project
  • [ ] copy the rest of the eunit macros into test/ltest-macros.lfe (full set of macros: https://github.com/lfex/ltest/blob/release/0.11.x/include/ltest-macros.lfe)
  • [ ] move lfe/test/ltest-macros.lfe to lfe/include/eunit.lfe
  • [ ] update test/clj-tests.lfe to include the test macros from the new location
• [ ] Add tests
  • [ ] the tests have already been written and cover all the major features of the DSL
  • [ ] copy these into lfe/test so that we can test the test-makers
• [ ] Document the eunit LFE wrappers / DSL
  • [ ] create a new documentation markdown file to let users know how to utilise the new eunit wrapper / DSL
  • [ ] update the LFE README.md to mention the new DSL support

Additional support:

• [ ] Update the ltest project to remove the macros (and pull them in as-needed from lfe/include/eunit.lfe)
• [ ] Update some projects that currently utilise the ltest macros and update them to use their new location in LFE
• [ ] Do lots of testing around all of these changes

[oubiwann]

I did a quick check on lines of code, and about 1/3rd of the eunit wrappers were brought into LFE.

Just 2/3rds to go ... 😉

[oubiwann]

Also, I should note that these wrappers have been used on numerous projects over the past 7 years (6 years in its current location). Only minor updates have been made in the macros over the last 4 years. All-told, this is stable code with a stable API.