Add a version filter while parsing guides

[marko-bekhta]

Fixes #351

• guides content changed a bit, so I've regenerated the samples and adjusted the tests
• I thought about starting with parsing the versions first and then getting the files by version. But then I thought that since we don't know which type of version it is (new or legacy) from the version file, we'd be checking if one file exists then the other, so here I kept the reading as is and added a version filter to it that should report if the expected version is missing.

[yrodiere]

But then I thought that since we don't know which type of version it is (new or legacy) from the version file, we'd be checking if one file exists then the other

TBH that's what I was expecting. Simple, but... simple :)

Anyway, LGTM except for one typo. Thanks!

[marko-bekhta]

"reason": "[parent] Data too large, data for [\u003chttp_request\u003e] would be [1030360888/982.6mb], which is larger than the limit of [1020054732/972.7mb], real usage: [1030360888/982.6mb], new bytes reserved: [0/0b], usages [request\u003d0/0b, fielddata\u003d494/494b, in_flight_requests\u003d0/0b]",

😖 it's probably time to look into that issue with the tests we've "patched" here #345 (comment)

[yrodiere]

"reason": "[parent] Data too large, data for [\u003chttp_request\u003e] would be [1030360888/982.6mb], which is larger than the limit of [1020054732/972.7mb], real usage: [1030360888/982.6mb], new bytes reserved: [0/0b], usages [request\u003d0/0b, fielddata\u003d494/494b, in_flight_requests\u003d0/0b]",

😖 it's probably time to look into that issue with the tests we've "patched" here #345 (comment)

This seems unrelated to the patch. You typically get this kind of error in OpenSearch when you send documents that are too large, or too many documents in a single bulk request.
Reducing the bulk size should fix it.