Conformance test fixes

[Shivani912]

closes #290
partially addresses: #320 (bisection)

UPDATE: moved single_peer/invalid_validator_set to multi_peer/malicious_validator_set because it seemed more appropriate.

QUESTION: Why do we don't run the multi_peer/... tests yet?

• Referenced an issue explaining the need for the change
• Updated all relevant documentation in docs
• Updated all code comments where relevant
• Wrote tests
• Updated CHANGES.md

[liamsi]

QUESTION: Why do we don't run the multi_peer/... tests yet?

I think when you had them ready and generated the JSON files, we added them to this repo without the rust code being ready?

tendermint-rs/tendermint/tests/lite.rs

Lines 193 to 196 in 27298f0

	async fn bisection() {
	// TODO: re-enable multi-peer tests as soon as the light client can handle these:
	// let dir = "bisection/multi_peer";
	// run_bisection_tests(dir).await;

[Shivani912]

QUESTION: Why do we don't run the multi_peer/... tests yet?

I think when you had them ready, we added them to this repo without the rust code being ready?

tendermint-rs/tendermint/tests/lite.rs

Lines 193 to 196 in 27298f0

	async fn bisection() {
	// TODO: re-enable multi-peer tests as soon as the light client can handle these:
	// let dir = "bisection/multi_peer";
	// run_bisection_tests(dir).await;

Possible, multi_peer tests fail at the moment in rust code. Seems to me it's not fetching headers from a witness. Will have to take a closer look though!

[liamsi]

LGTM 👍 I think it would be good if the missing multipeer tests were captured in an issue (if not already the case)

[Shivani912]

Thanks @liamsi ! Will do that :)