Tasicarlo issues 369, 370

[og113]

Deals with the raised in Issues #369 and #370, plus a couple small things:

• Comment about IDM renormalisation added to Model file
• Comment about git-lfs added to docs installation instructions
• WallGo.__version__ added to __init__.py, updated dynamically, and tested in tests/test_version.py
• removed WallGoCollision import fail warning
• added list of papers that have used WallGo to docs
• fixed small bug in validation of interpolation table
• fixed unpacking of 5 instead of 7 items in calls to EOM.wallPressure within EOM.findWallVelocityDetonation

Note that the updated docs for this PR can be read here: https://wallgo.readthedocs.io/en/tasicarlo-issue-370/

I've decided to make this PR now, as a reference for discussion, but some things still need doing:

• responding to the remaining issues in Two issues in the wall-velocity solver: (1) findWallVelocityDetonation unpacks 5 values from a 7-tuple + (2) hybrid-regime singular Boltzmann matrix #370
• adding tests for detonations

[og113]

Of the issues remaining, the easiest win is to expose forceImproveConvergence in WallGo's settings, so it can be set to True by the user.

[og113]

Of the issues remaining, the easiest win is to expose forceImproveConvergence in WallGo's settings, so it can be set to True by the user.

This is done now.

[pschicho]

Since this choice was deliberate by following other papers, I wouldn't add here an acknowledgment but rather in reply to the issue.

[pschicho]

Looks very good, thanks Oli. Had a few small questions.

[pschicho]

I think the issue was that this message was displayed even when the collision module was loaded. But now it wouldn't display at all, right?

[pschicho]

Can this self nesting cause any issues here?
Why not just write
self._validateInterpolationTable(self._rangeMin + 0.3 * (self._rangeMax - self._rangeMin))

[pschicho]

Maybe make clear that this needs to be done only once