Avoid code-walking in DEFINE-TESTCASE

Rewrite the DEFINE-TESTCASE macro so that it does not rely on code
walking.  This approach is lengthy, brittle and hard to expand. It
furthermore has some unexpected inconvenience.

The DEFINE-TESTCASE macro is rewritten so that it only instruments
assertions using signal and handlers.

org.melusina.confidence.asd

@@ -37,6 +37,7 @@
 		 (:file "assertion")
 		 (:file "result")
 		 (:file "testcase")
+		 (:file "interactive")
 		 (:file "entrypoint")))))
 
 (asdf:defsystem #:org.melusina.confidence/development

src/package.lisp

@@ -16,12 +16,22 @@
   (:export
    #:quit
    ;; Results
-   #:assertion-success
-   #:assertion-failure
-   #:assertion-condition
-   #:testcase-result
-   #:record-result
+   #:testcase-outcome
+   #:testcase-path
+   #:testcase-name
+   #:testcase-total
+   #:testcase-success
+   #:testcase-failure
+   #:testcase-condition
    ;; Testcases
+   #:assertion-path
+   #:assertion-name
+   #:assertion-argument-names
+   #:assertion-argument-values
+   #:assertion-form
+   #:assertion-type
+   #:assertion-description
+   #:assertion-condition
    #:define-testcase
    #:without-confidence
    #:*testcase-interactive-p*