- Added requirement that receivers are faulty on construction (1.8)
  - Clarified that validity can be set by the user code in 2.1.5

wip ExceptionHandlingSpec: C.2 ExceptionHandlingDecorator is throwing to implement skipping a transfer

* Added B.1.3 and B.1.4 : boost::numeric::bad_numeric_cast and boost::thread_interrupted are not treated
* Removed B.6 (behaviour for bad_numeric_cast)
* Removed C.2.8 (implementation for bad_numeric_cast)
* Re-numbered C.2.9 to C.2.8. It is the last section in C.2 and did not contain any anchors, so no references need to be changed.

ExceptionHandling spec: explicitly mention what returns true/false means (hasNewData or dataLost) each time

ExceptionHandlingSpec: Finished the proof reading except for simplifying C.2.4. Intentionally left as a single commit to simplify diffing

[wip] exception handling spec: remove A.2.2.5, which has become obsolete due to changes in the TransferElement spec

See B.9.2 of the TransferElement spec

[wip] exception handling spec: fix for async read transfers and initial values (also after recovery)

[wip] exception handling spec: many small corrections + start corrections about initial value after recovery for wait_for_new_data (still wrong!)