Extend bouncycastle rules to contain LTS versions

[jjohannes]

Resolve #188

[Vampire]

Hi there, are you sure just using latest version resolution is the right thing to do here? The lts versions will always be higher than the non-lts versions if I got it right.

2.73.x lts is based off 1.73 and only gets non-breaking changes. So if one dependent declares lts 2.73 and another needs breaking changes of the 20 years younger 1.999, it will resolve to old lts version and break.

[jjohannes]

Thanks for the clarification. Interesting versioning scheme....
IIUC, this means one could say, from the capability perspective:

• 2.73 corresponds to the 1.73
• 1.80 is therefore "higher" than 2.73 and the better "best guess" when doing select highest version

It might still not be always what the user wants, but that's the general issue that "select highest version" is only a "best guess" so that there is a default strategy. (See #185 for possibly changing something in the next major release.)

I made an adjustment that aligns the 1.x and 2.x version numbers in the Bouncy Castle rule: #226